Reframed funnel length as decision load: what the employer had to know, decide, type, trust, or correct before moving forward.
Product simplification / decision-load reduction
The Flash Funnel
The work was not making a long funnel look shorter. It was deciding which burden the employer should carry, and which burden the product should absorb.
Company / context
Indeed
Role
Product UX, simplification, mobile funnel strategy
Timeframe
Candidate source from Indeed deck
Proof strategy
Decision-load reduction and measurable funnel behavior
My role
Responsibility before artifacts.
Sorted funnel moments into keep, remove, defer, prefill, or explain so simplification had product logic instead of becoming taste or subtraction.
Connected the lighter mobile flow back to funnel behavior and experiment planning so the work could be judged by momentum and quality, not just by fewer screens.
Problem beneath the brief
The funnel was not just long. It was asking employers to think too much at the wrong time.
The legacy job-posting flow had 11 pages and 59 clicks, and it was built around a desktop rhythm. On mobile, the problem was not only length. Employers had to read, type, interpret, choose, trust, and correct before they had enough momentum. The work was to decide which decisions deserved attention, which could move later, and which the product could support directly.
Decision evidence
What the artifacts made discussable.
01 / Centerpiece artifact
The artifact treats friction as decision load, not screen count.
The first object makes the hidden cost visible: pages, clicks, reading, typing, context switching, quality worries, and dropoff all become part of the same decision-load picture.
Belief proved: simplification works when the product absorbs the right burden, not when it merely hides steps.
Old burden11 pages / 59 clicksReading, typing, context switches, quality worries, and mobile dropoff before enough momentum existed.
Responsibility sortKeep / remove / defer / prefill / explainEach input earns its place by job quality, confidence, timing, or product support.
New modelOne-page direction + checklist supportMake progress feel lighter while keeping the posting complete enough to trust.
Measurement logicDropoffRead burdenType burdenClicksCompletion behavior
Decision-load reduction map
02 / Responsibility sorting
Every field became a product decision: keep, remove, defer, prefill, or explain.
The useful move was sorting responsibility. Some information had to stay because it affected matching quality. Some could move later. Some could be easier input. Some needed explanation because the employer needed confidence before continuing.
The case should be remembered for responsibility sorting, not just a shorter flow.
KeepSignals that protect job qualityJob title, location, schedule, compensation, qualifications when they affect matching.
RemoveAccidental workQuestions, repetition, or navigation steps that add effort without improving the posting.
DeferDecisions that can waitAdvanced details move later when they interrupt early mobile momentum.
PrefillWork the product can absorbUse defaults, recommendations, and easier input when the employer should not have to start from zero.
ExplainMoments that need confidenceKeep extra guidance where the employer worries about job quality or hiring outcomes.
Keep / remove / defer / prefill board
03 / Mobile flow
The mobile path needed momentum and confidence at the same time.
The product direction moved toward one-page posting, checklist support, and progressive help. The goal was a lighter path that still felt complete enough to trust.
Fast can feel careless. The design job was making it feel lighter without making it feel thin.
01Start with the job shapeAsk only what unlocks useful progress.
02Use tap-based supportReduce typing where structured choices work better.
03Show checklist progressLet employers see what is complete and what still matters.
04Preserve posting confidenceFast should still feel complete, reviewable, and safe to publish.
Mobile momentum flow
04 / Measurement logic
The outcome was not just a nicer flow. It was a testable simplification model.
The evidence connects simplification to behavior: dropoff, read/type/click burden, phased experiments, and conversion signals. Metrics are not the whole story, but the model needed to be measurable.
Decision-load reduction should show up as better momentum, fewer unnecessary pauses, and healthier completion behavior.
Input burdenRead timeType timeClicks
Behavior signalStep lossCompletionConversion health
Experiment planBreak large bets into phasesMeasure sustainablyKeep quality checks visible
What success should mean
Less unnecessary decision burden, clearer momentum signals, and enough employer confidence to publish a useful job.
Experiment measurement frame
Decision journey
How the work unfolded.
01 / Burden
The old flow carried too much decision load
The visible count was 11 pages and 59 clicks. The hidden cost was heavier: reading, typing, context switching, quality worries, and decisions that appeared before the employer had enough confidence.
02 / Sort
Every field had to earn its place
Inputs were sorted by responsibility. Some needed to stay because they affected job quality. Some could move later. Some could be prefilling-supported. Some needed a clearer explanation. Some were accidental drag.
03 / Flow
Mobile needed momentum without carelessness
The new direction moved toward a simpler posting path with checklist-style support and progressive help, so the experience felt lighter without making the job feel incomplete.
04 / Evidence
Simplification had to stay measurable
The work connected interaction choices to funnel behavior, dropoff, read/type/click burden, and phased experiments. Fewer steps only mattered if the remaining steps were better placed.
Evidence boundary
Flash Funnel deck evidence, legacy funnel map, friction analysis, mobile dropoff, variant exploration, Sketch implementation files, and experiment-roadmap evidence.
Portfolio status: Needs public-safety review. Claims remain bounded to what the reviewed source set can support.
What changed / what the evidence supports
The work reframed a heavy employer workflow into a lighter mobile posting direction by sorting decision burden: what to keep, remove, defer, prefill, explain, and measure.
Reflection
My contribution was making friction specific. The issue was not simply that the funnel was long. It was that too many small decisions were in the wrong place, and the product could carry more of that burden without taking away necessary employer judgment.