Project Management for Engineers
summary
Practical framework from ideation to handoff with concrete tools and numbers: use an Impact Effort Matrix to coalesce ideas, run a 3-month trial for any new process, collect stakeholder votes (three each) to pick priorities, and document outcomes as Success Statements like “increase sales 15% by integrating a third‑party API” or “save $500/month in storage.” Start with a Google Doc MVP, write a migration plan, schedule recurring SOP meetings (every nine weeks), automate reporting and rotate glue work so processes survive personnel changes.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:28Engineer mindset pitfalls
- 2:10Project management mindset
- 5:00Building team consensus
- 7:08Testing process changes
- 11:03Migration plan for changes
- 12:09Prioritizing tasks
- 18:27Understanding stakeholders
- 21:14Stakeholder communication strategies
- 26:06Stakeholder voting
- 26:49Simple team processes
- 32:03Documenting success
- 36:16Practice success statements
- 40:39Celebrating progress
- 45:55Marketing team achievements
- 51:23Documenting processes
- 55:16Q&A
related talks
39mProject Management for Engineers
40mThe Joys of Managing Engineering Teams
09m"The Joys of Managing Engineering Teams"
10mStart with an exit in mind
46mManaging The Process
42mStep by step approach to create meaningful impact
33mAligning Goals & Processes between Engineering & Product
10mFocus on project value using businesses strategy