PracticeProduct Judgment

Applied~2–3 minChoose, then see feedback · no writing

Approve the build?

Twelve interviews, five workarounds

The situation

Three weeks of discovery on an approvals concept wrap up with a synthesis memo to product-team@ and leadership@. Twelve interviews with ops leads. Headline: strong validation, recommend we build.

Ravi Deshmukh · Product: “Full notes are in the shared drive. Happy to walk anyone through them, but I think the picture is clear.”

The memo says: 'Headline: strong validation. Recommend we build.' The guide, the recruitment detail and Ravi's notes are attached. First say what survives; then say what happens next.

What you can see (7) · tap a card to read it

›E01 · Themes

Approvals are painful (11/12): 'bottleneck', 'chaotic', 'frustrating', 'black hole'. Strong interest in automation (10/12): ten reacted positively to the concept when walked through the mockups; several asked when it would be available. Mobile matters (7/12), unprompted in three cases. Integration is table stakes (9/12), though the specific tools varied a lot.

›E02 · Quotes and rating

'Honestly, if you had this today I'd use it.' 'This is exactly the kind of thing we've been looking for.' 'The approval chain is a nightmare. Anything that fixes it, I'm interested.' 'I could see this saving us a lot of time.' Concept rating after seeing three mockups: average 4.2, nine of twelve gave a 4 or 5. The memo doesn't report the answers to questions 2 and 3, and no commitments were asked for.

›E03 · Recommendation and risks

Move to build, targeting professional services and SaaS for v1 with manufacturing as a fast-follow; scope is the approval chain plus mobile approve/reject, integrations deferred to v2. Risks listed: manufacturing may be a weaker segment (three of the four lowest ratings), integration scope unclear, two participants asked about pricing and were deflected.

›E04 · Appendix: interview guide

1. Tell us about your role and team. 2. How would you describe your current approval process? 3. What are the biggest frustrations with it? 4. (show mockups) What's your reaction to this? 5. Would you use something like this? 6. How much time do you think it would save you? 7. What would we need to have for you to consider switching? 8. On a scale of 1 to 5, how valuable would this be to your team?

›E05 · Who was interviewed

Twelve ops leads at companies of 80 to 400 people. Nine from the inbound waitlist, three intros from Siobhan's network. Two logistics, four professional services, three SaaS, three manufacturing. Sessions 45 to 60 minutes, remote.

›E06 · The ratings behind the segment call

The two 3s were both manufacturing; the one 2 was also manufacturing. The v1 segment recommendation (professional services and SaaS) rests on manufacturing giving the lowest ratings to the mockups. The rating question was 'how valuable would this be to your team', asked after the mockups.

›E07 · Ravi's notes on how approvals work today

From the answers to questions 2 and 3. 7 of 12 run approvals through email threads. 3 keep a shared spreadsheet that one person updates by hand. 2 pay for a forms tool, at £40 and £120 a month, and say it doesn't handle the approval chain. None has built anything in-house.

Step 1 of 2

What in the research holds up?

Your first choice is kept. Changing your mind later counts as a retry.