Submit the workflow your team hates. I will select one useful problem, map the current mess, redesign the path, build the smallest useful fix, and publish what happened—including what did not work.
Gather submissions with the user, trigger, steps, failure points, workaround, volume, cost, and desired result.
Choose a process that is specific enough to improve, common enough to teach from, and safe enough to document.
Publish the actors, systems, handoffs, delays, duplicate work, ownership gaps, and the evidence behind the diagnosis.
Remove steps, combine decisions, clarify ownership, automate only where useful, and define the smallest testable change.
Create the prototype, worksheet, workflow, script, interface, or operating rule needed to test the redesigned process.
Show the before and after, what changed, what failed, what it cost, what evidence improved, and whether the project continues.
The challenge guarantees a documented attempt, not a predetermined success story. A useful failure with clear evidence belongs in the Failure Files rather than being edited into a victory lap.
The free playbook helps organize the user, trigger, current path, failure points, ownership, evidence, better path, and smallest useful test.
The Office Hours builder creates the structured brief. Choose “Operations and workflow” and allow an anonymized public teardown when appropriate.