Firstclub
Product Design Manager · founding team
[TO VERIFY] dates
Getting Product, Engineering and Design to one decision
A disagreement that mattered, and how the team reached a call it could live with. Influence is the hardest thing to evidence and the most valuable.
- Role
- Product Design Manager — convening the decision
- In the room
- [TO VERIFY] Product · Engineering · Ops · founders?
- The tension
- [TO VERIFY] one line
- Timeline
- [TO VERIFY] dates
- Outcome
- [TO VERIFY] the decision, and what followed
The trap to avoid on this page
- Do not write “I collaborated with Product and Engineering.” It says nothing.
- Write what each side wanted, why each was reasonable, and what changed because you were in the room.
- At an early-stage company the founders are often in this conversation. If they were, say so — disagreeing well with a founder is a strong signal.
The disagreement
State every position charitably.
Answer these
- What did Product want, and what were they optimising for?
- What did Engineering raise — effort, architecture, risk, data availability?
- What did Operations raise? In quick commerce this is usually the constraint that actually decides things.
- What did Design believe, and on what evidence?
- Why was it genuinely hard? A story where one side is obviously wrong isn't a story.
Why it was stuck
Answer these
- Was it a values conflict, an information gap, an ownership vacuum, or a deadline?
- How long had it been going, and what had already been tried?
- What was the cost of staying stuck?
What I did
The mechanism, concretely.
Answer these
- Did you reframe the question, and to what?
- Did you build something — a journey map, a decision framework, three costed options, a prototype?
- Did you change who was in the room, or the order of the conversation?
- What principle did you get the group to agree on before discussing solutions?
Key decisions
The call, and the ones underneath it.
-
Name the decision
Decision State it in one sentence, in plain language.Alternatives What else was genuinely on the table?Rationale The actual reason, not the tidy retrospective one.Trade-off What did it cost? A decision with no cost is not a decision.Consequence What happened because of it? -
Name the decision
Decision State it in one sentence, in plain language.Alternatives What else was genuinely on the table?Rationale The actual reason, not the tidy retrospective one.Trade-off What did it cost? A decision with no cost is not a decision.Consequence What happened because of it? -
Name the decision
Decision State it in one sentence, in plain language.Alternatives What else was genuinely on the table?Rationale The actual reason, not the tidy retrospective one.Trade-off What did it cost? A decision with no cost is not a decision.Consequence What happened because of it?
My role
-
Owned
[TO VERIFY] — problem framing? product direction? a specific flow you designed yourself?
What you directly owned and executed. -
Co-owned
with which PM or designer, and on what exactly?
Jointly owned with someone else. -
Influenced
what did you change someone's mind about, and what did they think before?
You materially changed the direction without executing everything. -
Enabled
name the designer, what they owned, and what you supplied — context, critique, a constraint removed?
A team member executed it; you gave direction and support. -
Team outcome
what should be credited to the team rather than to you?
The result belongs to the wider team.
What it changed beyond this decision
The second-order effect is the leadership signal.
Answer these
- Did the way the team makes this kind of decision change afterwards?
- Did Design get involved earlier on the next thing?
- Did the framework or ritual get reused?
- Did it shift the roadmap, the scope, or what the team stopped doing?
Outcome
Any of these
- Product: what shipped, and what it did.
- Process: decision speed, earlier design involvement, fewer reversals.
- Business: effort avoided, complexity removed, a bet not taken.
Reflection
One honest paragraph
- Whose concern did you underweight?
- What would you convene earlier next time?
Evidence standard — from your knowledge base, §21
- Verified — explicitly stated in your source material. Safe to publish.
- Strongly supported — derivable from several source statements. Safe to publish.
- Inferred — a reasonable reading, not stated. Use as a prompt for you to confirm, never as copy.
- To verify — missing. This is what the dashed blue text on this page is.
- Portfolio copy uses only the first two. I have written nothing above that standard.