ADVANCED · 8 MODULES · 64 LESSONS

Product Judgment and Discovery as an Investment

Decide with numbers what deserves to be built each quarter: prioritize by business outcome, buy just enough evidence before investing, and learn to say no.

For you if
You decide what goes into your team's quarter, and there are more requests than capacity.
By the end
You'll know how to prioritize with RICE, ICE, and cost of delay, size opportunities, and read evidence to continue, pivot, or stop.
You need
A part in product decisions, now or soon. No coding or design skills needed.
  1. 01Outcomes, not outputs8 LESSONS
    1. Introduction: twelve deliverables and nothing moved
    2. What an output is
    3. What an outcome is
    4. The build trap
    5. Why this belongs to whoever leads
    6. What makes a good outcome
    7. From initiative to metric
    8. Project: audit of Granero's quarter
  2. 02The value chain8 LESSONS
    1. Introduction: from the team's work to Granero's money
    2. The four links of the chain
    3. From task to capability
    4. From capability to value for the store owner
    5. From value for the store owner to business value
    6. Tracing an initiative end to end
    7. When the chain breaks
    8. Project: Granero's backlog, traced
  3. 03Prioritizing with RICE and ICE8 LESSONS
    1. Introduction: three directors, eight initiatives, 24 weeks
    2. Why prioritize with a method
    3. The RICE formula
    4. Reach and impact
    5. Confidence and effort
    6. ICE and when to use it
    7. The limits of scoring
    8. Project: Granero's backlog, prioritized
  4. 04Opportunity sizing8 LESSONS
    1. Introduction: how much is each bet worth?
    2. Why size before you build
    3. The opportunity sizing formula
    4. Reachable stores and baseline
    5. Estimating the lift
    6. Assumptions and ranges
    7. Comparing opportunities
    8. Project: the size of Granero's bets
  5. 05How much to build in order to learn8 LESSONS
    1. Introduction: the prototype that convinced the CEO
    2. What an MVP really is
    3. Scope versus learning: how much to invest before building
    4. The cheapest experiment that can prove you wrong
    5. The walking skeleton: approving the thinnest end-to-end version
    6. Cutting scope without cutting value
    7. MVP anti-patterns and the biases that feed them
    8. Project: the approved scope of the uncertain bets
  6. 06Assumptions, experiments, and prototypes for deciding8 LESSONS
    1. Introduction: buying evidence before spending the quarter
    2. Facts and assumptions: thinking about the bet in probabilities
    3. When a prototype built with AI helps you decide
    4. What each piece of learning costs
    5. Evidence inside RICE: persevere, pivot, or kill
    6. The riskiest assumption
    7. Learning the customer's domain: interviews and teach-back
    8. Project: validation plan for store-owner credit
  7. 07Saying no and the roadmap as bets8 LESSONS
    1. Introduction: the pilot results are in
    2. Opportunity cost: what you don't do by doing this
    3. Cost of delay, calculated by hand
    4. WSJF: shortest job with the highest cost of delay first
    5. The roadmap as bets
    6. Saying no well
    7. Communicating the decision
    8. Project: Granero's quarterly roadmap
  8. 08Project: Granero's bets for the quarter8 LESSONS
    1. Introduction: the December 10 board meeting
    2. The outcome and the value chain
    3. The scored backlog
    4. The size of the bets
    5. The riskiest assumption and what the evidence said
    6. The minimum scope of each bet
    7. The sequence and the no list
    8. Final project: the bets document and its defense before the board
Reviews

What students say

These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.

No approved reviews yet.

Be the first to share your experience!

SEC. 06 · THE STUDIO

Why this studio exists

For decades, building software belonged to technical profiles with years of training, and getting a digital product into the real world took companies months or years. No-code and AI have narrowed that gap, but the knowledge is still held by a few.

Tech Benders exists to open that knowledge up, so business teams and non-technical teams can put their ideas into production with the right technical decisions behind them. AI does what you ask of it. Without a technical base, what it builds may not scale with your company’s ecosystem, and its costs can run away over time.

The team knows the pains of large organizations and the speed at which they have to move. It brings solution architecture, data engineering, product built end to end from back end to front end, and daily work with AI. Software that solves what you need in days, not months, with the cost of AI kept in check.

Founders

The studioRead about Tech Benders →

Write to ushi@techbenders.io

Made with Wislab