✳flâneur — a map of the web's best reading

How to “Loop In Engineering” – PMTechLessons

pmtechlessons.com · 940 words · saved by 1 readers

Common advice for new product managers is to “loop in engineering” early in the process of feature development. There’s a class of advice that I personally take issue with: advice where the plan and the goal are the same. If your goal is to “loop in engineering”, your plan to do so can’t also be “to loop in engineering”. See also: common presentation advice, “talk slower”, which you can achieve if you simply “talk slower”. 🙄 Here’s my advice for turning this goal into a plan. “Looping in engineering” is ultimately an action. To develop the proper process, we first need establish for ourselves why we’re going to engineering. Ideas and Ownership One reason is to broaden ownership of a feature. A simple approach for turning masons into missionaries is for developers to have the idea for the feature they’re working on themselves. Bringing an unmet user need to the team and asking for their input works as an ad hoc brainstorm. Once someone shows a particular interest, you can work with the

Common advice for new product managers is to “loop in engineering” early in the process of feature development. There’s a class of advice that I personally take issue with: advice where the plan and the goal are the same . If your goal is to “loop in engineering”, your plan to do so can’t also be “to loop in engineering”. See also: common presentation advice, “talk slower”, which you can achieve if you simply “talk slower”. 🙄 Here’s my advice for turning this goal into a plan. Define Your Goal “Looping in engineering” is ultimately an action. To develop the proper process, we first need estab

Explore this link on the map →

saved by

related reading