The hottest Project management Substack posts right now

And their main takeaways
Category
Top Technology Topics

The worst project manager ever: a total idiot

Respectful Leadership • 54 implied HN points • 22 Mar 23
💼 Business Management Leadership Project management Team Dynamics
  1. Qualities of a great project manager are qualitative and include moral convictions, confidence, and perceptiveness, rather than just formal credentials.
  2. Respect is key in achieving excellent project management: respecting time, understanding priorities, and communicating effectively define a good project manager.
  3. Dealing with changing priorities respectfully involves supporting the team emotionally, being transparent about costs and time estimates, and facilitating collaboration between different levels of staff.

What Is Yak-shaving?

Load-bearing Tomato • 7 implied HN points • 15 May 24
🕹 Technology Software Development Product Management Technical Debt Project management Task management
  1. Yak-shaving happens when you start a task and then realize it leads to a bunch of other unrelated tasks that you didn't expect. It's like going to wax your car and ending up at the zoo, needing to shave a yak instead.
  2. This situation often arises from not understanding the dependencies of a task before you start working on it. Properly planning and identifying prerequisites can help avoid getting tangled in unnecessary tasks.
  3. To prevent yak-shaving, it's important to scope tasks carefully and flag assumptions early. Being aware of how tasks connect can help you manage time better and avoid going down rabbit holes.

Academia vs Business

inexactscience • 19 implied HN points • 02 Mar 23
💼 Business Data Analysis Business strategy Market research Project management Organizational Behavior
  1. Academia and business both use data to solve problems, but they focus on different aspects. In academia, getting the right answer is more important than how fast you get it.
  2. The speed-quality frontier shows that in academia, quality matters a lot, which means projects can take years. In business, speed is key, so decisions often get made quickly.
  3. Feedback loops are faster in business. Companies test ideas against real market data quickly, while in academia, feedback often comes later from peer reviews, slowing down the process.

Building CAUSL - Episode 8: The Growth Conundrum

CAUSL Effect • 19 implied HN points • 07 Apr 23
💼 Business Entrepreneurship Consulting Growth Strategy Project management Team Building
  1. The team has learned a lot about managing projects by working closely on them, even though it's just two people. This hands-on experience has been valuable and helped them understand client needs better.
  2. Finding ways to grow is a major concern for the team since they are still small. They realize the need to adapt and look for new opportunities for their business.
  3. With new team members joining who bring different skills, they are expanding their services. This helps them to not only grow but also offer more value to their clients in areas like product leadership.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

"Single panes of glass" are horrible

Counting Stuff • 21 implied HN points • 30 Mar 23
🕹 Technology Data Analysis User Interface Project management
  1. Single panes of glass in technology often promise magic but fail to deliver in a meaningful way
  2. The concept of 'single panes of glass' in tech is fundamentally flawed because it doesn't mirror the efficiency and specialization seen in physical interfaces like those in transportation
  3. Project requests for 'single panes of glass' tend to lead to complex, unsustainable solutions that are difficult to manage and maintain over time

The Blurred Line Between Methodology and Framework

Building Rome(s) • 13 implied HN points • 24 Aug 23
🕹 Technology Methodology Framework Software Development Agile Project management
  1. The role of a Technical Program Manager (TPM) involves defining and implementing the methodology and framework for software development projects.
  2. Methodologies provide general principles while frameworks offer specific plans of action.
  3. It's important for TPMs to be flexible in choosing the right methodology and framework based on the project's specific needs and requirements.

18/36 :Product Discovery - Risks & Mitigations

Product Mindset's Newsletter • 17 implied HN points • 21 May 23
💼 Business Risk management Technology Project management Software Development Strategic Planning
  1. Understanding product risks involves assessing the impact of uncertainty on developing a product.
  2. Risk management in IT projects is crucial for maximizing results, effective communication, and allocating funds for high risks.
  3. Managing risks involves identifying, analyzing, and mitigating them through strategies like avoiding, reducing likelihood, and reducing impact.

Reading: How Big Things Get Done

Wetware Snippets • 5 implied HN points • 11 Mar 24
💼 Business Project management Success Factors Risk management
  1. Modularization is key in project management. Breaking down a large project into repeatable modules simplifies delivery.
  2. Different projects have distinct distribution patterns, impacting their likelihood of success. Thin-tailed distribution projects are more likely to be on time and budget.
  3. Lessons from the book can be applied to personal projects like kitchen renovation or holiday planning. It's a valuable read for project managers and those tackling significant endeavors.

6/36 - Crafting a Problem Statement

Product Mindset's Newsletter • 17 implied HN points • 19 Feb 23
💼 Business Problem Solving Communication Project management Consulting Innovation
  1. A problem statement is a clear explanation of an issue or challenge that needs to be changed.
  2. Defining a problem statement requires addressing the 'five w's and one h': what, why, when, where, who, and how.
  3. Crafting a problem statement is vital for projects as it sets the foundation for research and development, ensuring all team members know the problem and its importance.

Scrum - use the good parts too!

Nikola’s Substack • 1 HN point • 20 Apr 24
💼 Business Management Productivity Teamwork Project management Leadership
  1. Consider streamlining meetings in Scrum - fewer, more effective meetings can be beneficial.
  2. Simplify story points and estimations in Scrum by setting straightforward guidelines to avoid confusion and enhance planning.
  3. Maintain the core strengths of Scrum like sprint structure and the Scrum Master role, while adapting them to best suit the team and project needs.

[in case you missed it] Data Science Weekly - Issue 437

Data Science Weekly Newsletter • 19 implied HN points • 10 Apr 22
🕹 Technology Data science Machine Learning Artificial Intelligence Software Development Project management
  1. Distribution shift is a big challenge in machine learning. If we ignore how data changes in the real world, our models may fail.
  2. Tech apprenticeships are becoming more common and are a great way to learn while earning money. They help people start new careers in tech, even without a degree.
  3. There's ongoing research to give computers common sense. This could help AI understand the world better and make smarter decisions.

Quitting

Fish Food for Thought • 5 implied HN points • 20 Dec 23
💼 Business Decision-making Leadership Strategic Planning Project management Technology
  1. Quitting can sometimes be advantageous, even though it's often seen negatively in society.
  2. Knowing when to quit is as important as knowing when to persist, especially in decision-making and project management.
  3. Strategic quitting requires establishing clear criteria, listening to experienced voices, and making rational decisions for better outcomes.

Episode 12: Burkhard on Qt Embedded Systems

burkhardstubert • 39 implied HN points • 30 Nov 20
🕹 Technology Embedded Systems Software Development Freelancing Project management
  1. Freelancers should focus on providing value to clients by saving them time. Clients will often pay more to have their time freed up for important tasks.
  2. It's important for freelancers to continually improve their skills and showcase successful projects to increase their perceived value. This can be done through side projects and sharing expertise online.
  3. Choosing the right pricing strategy is crucial for freelancers. Understanding different methods like value-based pricing can help in setting fair rates that reflect the value provided to clients.

The Scrum Survival Guide: How to Make Scrum Work (Maybe)

Rethinking Software • 2 HN points • 21 Sep 24
💼 Business Project management Agile Methodology Team Dynamics Organizational Behavior Software Development
  1. Using longer sprints can give teams more freedom and reduce stress over estimating work. It allows developers to manage tasks more effectively without getting stuck on details.
  2. It's important for developers to have control over their meetings and tools. Letting developers run their own stand-ups and choose simple tools can improve efficiency and morale.
  3. Teams should focus on collaboration and flexibility. Allowing for specialization in tasks and removing unnecessary management roles can lead to better job satisfaction and productivity.

Episode 20: Burkhard on Qt Embedded Systems

burkhardstubert • 19 implied HN points • 02 Aug 21
🕹 Technology Embedded Systems Consulting Software Development Project management
  1. Value pricing focuses on what customers are willing to pay and guarantees results. This approach helps both the client and consultant by reducing uncertainties about costs and outcomes.
  2. Offering multiple pricing options increases the chances of acceptance. When customers can choose between different payment plans or benefits, they feel more in control and are more likely to say yes.
  3. Switching to pre-payment and reducing work hours allows more time for business operations and future planning. This means less stress and better business health for consultants.

Why hire Technical Program Managers when we have Product Managers

Building Rome(s) • 7 implied HN points • 13 Feb 23
🕹 Technology Product Management Project management Tech Roles Development Process Collaboration
  1. Hiring Technical Program Managers can add value by keeping track of complex project schedules and dependencies.
  2. Product Managers can sometimes handle the work of TPMs, especially in early stage startups.
  3. As organizations grow, there may be opportunity costs in not hiring TPMs to ensure effective communication, alignment, and risk mitigation.

Explore and Exploit: Importance of Side Projects

trydeepwork • 1 HN point • 02 Jun 24
💼 Business Project management Personal Development Productivity Self-Improvement Career growth
  1. It's important to balance trying new things (exploration) and focusing on what you already know (exploitation). This balance keeps life interesting and engaging.
  2. Side projects can be valuable for exploring your interests. Don’t feel guilty about them; they help prevent burnout by adding novelty.
  3. When starting new projects, label them as exploratory or exploitative. This helps you know when it's okay to abandon something and when you should commit fully.

Revisiting: Why Scrum is the Wrong Way to Build Software Pt.1

Rethinking Software • 1 HN point • 09 Sep 24
🕹 Technology Software Development Agile methodologies Project management Team Dynamics Product Management
  1. Scrum gives all product decision power to the Product Owner, leaving engineers to persuade rather than decide. This can create frustration for engineers who want to contribute to product direction.
  2. Many companies confuse the Product Backlog with engineering tasks, making it hard for engineers to focus on their work without interference. Keeping these backlogs separate can help maintain clear roles.
  3. The way Scrum is often implemented leads to engineers being sidelined in decisions about what to build, showing a need for better practices to include their input in product decisions.

Working at Google: Maps Continued

Life Since the Baby Boom • 3 HN points • 27 Feb 23
🕹 Technology Software Development Corporate culture Patents Code Reviews Project management
  1. Marissa Mayer oversaw Google's 'Local' division, focusing on local ads and services.
  2. The acquisition of Zagat by Google faced internal resistance and eventually Zagat was spun out to another company.
  3. Code reviews and the pursuit of perfection in coding can lead to conflicts and differing perspectives among software engineers.

Little Tasks, Little Trust

Rethinking Software • 1 HN point • 11 Oct 20
💼 Business Management Work Culture Productivity Software Development Project management
  1. Breaking work into small tasks can make workers feel like they have no creative control. When given bigger responsibilities, they feel trusted and more motivated to contribute ideas.
  2. Focusing too much on metrics and small tasks can take away from the bigger picture of a project. It can lead to a lack of respect for individual skills and creativity.
  3. Estimating small tasks accurately is tough. It's easy for simple tasks to become complicated, leading to time wastage and misunderstandings in the project.

Improve your Productivity as a Solopreneur with Multiple Micro-Startups and a Full-Time Job

layoffpreneur • 0 implied HN points • 17 Mar 23
💼 Business Productivity Time management Project management Stress management
  1. Managing time effectively is crucial for solopreneurs with a full-time job. Tools like time blocking and task prioritization can help.
  2. Project management tools like Trello and Asana are essential for handling multiple micro-startups and a full-time job.
  3. Taking breaks, practicing self-care, and using automation tools can help solopreneurs stay productive and avoid burnout.

10x Controlling Project Skies

10xManager • 0 implied HN points • 06 Feb 24
🕹 Technology Engineering Leadership Project management Data Analytics Software Development
  1. Visibility is crucial for effective engineering leadership, just like air traffic controllers oversee busy airspace.
  2. Gaining visibility into software development processes helps in anticipating challenges and optimizing team performance.
  3. Engineering leaders can benefit from tools that offer comprehensive visibility and insights for managing projects successfully.

Season 03 - Newsletter 05 --> Making an impact in the Maze: Finding the Gray Areas

Product Hustle Stack Newsletter • 0 implied HN points • 27 Nov 23
💼 Business Project management Communication Skills
  1. Find opportunities in big organizations by looking for gray areas and interesting projects.
  2. Build trust and influence by getting wins under your belt and collaborating with peers as allies.
  3. Communicate effectively by acknowledging past efforts, addressing motivations, and customizing messages to each stakeholder.

Software Projects: Sink or Swim

Bismuth • 0 implied HN points • 14 Jun 24
🕹 Technology Software Testing Documentation Technical Writing Project management
  1. Establishing and maintaining consistent patterns in a software project is crucial for long-term maintainability and success.
  2. Thorough testing, especially of core business logic and high-risk features, is essential to prevent bugs and ensure code maintainability over time.
  3. High-quality documentation is vital for attracting users, helping new contributors, and ensuring the long-term success and growth of a software project.

Top 5 Kanban Tools to Streamline Your Workflow

Weekend Developer • 0 implied HN points • 21 Apr 23
🕹 Technology Tools Productivity Workflow Software Project management
  1. Using a physical wall with sticky notes can be a simple and effective way to create a Kanban board for task management.
  2. Draw.io is a versatile tool that includes a Kanban template and can help in creating flowcharts and diagrams.
  3. Trello and Jira are among the top Kanban tools, with Trello being simple and suitable for personal projects, while Jira is commonly used in organizations and offers a free version for small teams.

Quality Engineering Basics: Prioritizing Bugs

QUALITY BOSS • 0 implied HN points • 18 Mar 24
🕹 Technology Software Development Quality Assurance Project management Automation
  1. Understanding how to prioritize bugs is key for efficient quality engineering. It's important to have a common agreement on what each priority level means.
  2. Using a matrix to categorize bugs by their scope and impact can help in deciding their priority. This method allows teams to see which bugs are more urgent and need immediate attention.
  3. Automation tools, like GitHub actions, can streamline the bug prioritization process. They can help automatically assign priority based on set parameters, saving time and reducing errors.

On communicating why software is late

Thoughts from the trenches in FAANG + Indie • 0 implied HN points • 17 Jun 23
🕹 Technology Software Development Project management Agile Methodology Stakeholder engagement
  1. Software projects often experience delays, especially when creating new software. It's important for both engineers and stakeholders to work together and understand how to communicate about these delays effectively.
  2. Clear communication about the project's delay is crucial. Everyone should know the new expected delivery date, what caused the delay, and what is being done to fix it.
  3. It's helpful to regularly share updates about the project's progress. Using a simple color system can show how likely the project is to meet deadlines, helping everyone stay informed and manage expectations.

Segregate resources and good hygiene between AWS accounts

Thoughts from the trenches in FAANG + Indie • 0 implied HN points • 06 Jun 23
🕹 Technology Cloud Computing Software Engineering Data security Project management Resource Management
  1. Using different AWS accounts for each project helps keep resources separate and makes billing easier. This way, it's simple to track costs for each project.
  2. Having separate accounts reduces confusion and complexity for engineers. It keeps projects organized, making it easier to find the resources they need and limits mistakes.
  3. Segregated accounts also improve security, as a problem in one account won't affect others. This protects against errors and minimizes potential damage from mismanaged access.

The Pareto Principle

André Casal's Substack • 0 implied HN points • 22 Aug 24
💼 Business Entrepreneurship Product Development User Feedback Project management Innovation
  1. The Pareto Principle, or the 80/20 rule, shows that a small part of your efforts can lead to most of your results. Focus on the most important tasks to make big improvements.
  2. Iterating on your product after each test drive helps you learn and improve quickly. Getting feedback from real users is key to making it better.
  3. Making your product easier to use can greatly enhance user experience. Simple changes like clearer instructions and automatic installations can solve a lot of pain points.

Season 03 - Newsletter 01 --> 5 Things I did as Product Manager to tame a monster initiative

Product Hustle Stack Newsletter • 0 implied HN points • 23 Jul 23
💼 Business Management Leadership Product Management Project management Team Collaboration
  1. Anchor conversations on a single currency like customer centricity for better decision-making
  2. Embrace a 'pirate mentality' for fast, bold, and unified team progress in complex projects
  3. Utilize frameworks like Radical Delegation, LNO Effectiveness, and Rituals for efficient project management