7 Views
Product development is a challenging journey.
Itโs not just about shipping features โ itโs about people, decisions, process, and culture.
Everything Starts with People
- Product: What to build
- Process: How we build
- Culture: Why it works
As a PM, What Do I Really Decide?
- Itโs not always clear โ VPs, stakeholders, engineers, and even the CEO shape the product.
- Power is shared. Influence matters.
- Everyone is a designer โ if you shape the outcome, youโre designing.
What Really Defines Waterfall?
Even a โ2-week sprintโ can still be waterfall if:
- Requirements โ Design โ Code
- Output-focused
- All risks appear at the end
Waterfall โ Discovery
Discovery Means Tackling Risk Early
Discovery = De-risking the work before writing code:
- Value: Will users use it?
- Usability: Can users use it?
- Feasibility: Can we build it?
- Viability: Will it work for the business?
Dual-Track Product Development
Balance discovery and delivery:
- Build the right product vs. build the product right
- Fake it before you make it
- Donโt scale until you must
- Design sprints โ Delivery sprints
- Discovery never ends
PM Pain: OKRs
If OKRs are so great, why are they painful?
- Culture resists change
- OKRs should focus on outcomes, not outputs
- Features โ Outcomes
๐ก Engineers Not Excited?
At Aumet Inc, we do things differently:
- Let engineers meet users
- Share the full business context
- Encourage them to invent, not just code
What Really Defines Product-Market Fit?
You might have product-market fit if:
- It solves a must-have problem
- You have high retention
- It grows organically
Stay Tuned for Aumet Pulse
Weโre sharing how we build scalable healthcare tech with AI at its core.
Tags:
#ProductManagement #TechLeadership #StartupLife #DigitalTransformation #BuildInPublic
#Innovation #DesignThinking #CustomerExperience #GrowthMindset #ProductCulture #Aumet #Pulse
Yahya Najjar – Aumet COO
