2023-02-09
1448
#career development
Bart Krawczyk
159183
102
Feb 9, 2023 â‹… 5 min read

The good, bad, and ugly of product management

Bart Krawczyk Learning how to build beautiful products without burning myself out (again). Writing about what I discovered along the way.

Recent posts:

A Guide To Choosing The Right PLM Software

A guide to choosing the right PLM software

At its core, product lifecycle management (PLM) software is a tool designed to manage every aspect of a product’s lifecycle.

Kayode Adeniyi
Dec 24, 2024 â‹… 4 min read
How To Use Scenario Analysis To Innovate In Product Development

How to use scenario analysis to innovate in product development

Scenario analysis is a strategic planning tool that helps you envision a range of possible future states and the forces behind them.

Monica Dhiman
Dec 23, 2024 â‹… 5 min read

What does a fractional product manager do?

A fractional product manager (FPM) is a part-time, contract-based product manager who works with organizations on a flexible basis.

David Theil
Dec 20, 2024 â‹… 6 min read
Use Case Vs. User Story- How And When To Use Each

Use case vs. user story: How and when to use each

As a product manager, you express customer needs to your development teams so that you can work together to build the best possible solution.

Zeynep Cansu Yildirim
Dec 19, 2024 â‹… 3 min read
View all posts

One Reply to "The good, bad, and ugly of product management"

  1. Product Managers without the software engineering skills and experience have been a disaster to the software industry. In decades past, successful software engineering teams were led by a senior software engineer, who managed the project, understood the product and the market for it, had good “people skills” in dealing with customers, managers, and team members, and understood business and the financial sides of the software business. Non-technical project managers reported to the senior team leader who offloaded the non-technical paperwork to that project manager (usually needed on larger projects, but not smaller ones).

    The team lead also handles the Agile methodology applied to the project, usually applying the Agile Manifesto principles according to the attributes of the team and project, not any of the modern “agile methodologies” that are really only workable in manufacturing.

    Even today, that process works. I know because 1) I understand how it works across disciplines, and 2) because I’ve “been there, done that”.

    The benefits to the employer, when the process is used in software development properly:
    1 – Project is completed on time or before.
    2 – Project is completed with better quality and fewer bugs.
    3 – Project is usually delivered with more features, even in the minimum viable product (MVP stage.
    4 – Project is built with fewer people, and little to no non-technical people.

    Creating software is not a bunch of coders assembling widgets where most everything is known at the time of assembly (where modern agile principles work fairly well). At the time software is written, it involves about 60% research, 30% creativity and artistry, and 10% actually coding. That is why hiring developers by assessing their skills by some “code challenge” quiz is such a bad idea. Do you want to hire those who memorize trivia well, but are not skilled at deductive reasoning so they can’t figure out their projects very well, or do you want to hire developers who learn, adapt, know where the answers are found, and are strong in deductive reasoning – so they can solve the unique problems of each project and adapt faster to newer technology?

Leave a Reply