Somewhere in your company right now, someone is building a deck. They'll spend two weeks on it — sharpening the framing, tightening the headlines, getting every chart to line up — and then they'll present it. And that presentation, the first time anyone outside the room sees the thinking, is the single most expensive moment to find out it's wrong.

By the time work is polished, it's also committed. The hours are spent, the story is set, and everyone in the room can feel how much it would cost to start over. So the disagreement that should have surfaced in week one surfaces at the reveal instead — if it surfaces at all.

We do the opposite, on purpose. At Storyworthy, showing unfinished work isn't a personality quirk or a sign we ran out of time. It's how we work.

A finished deck says "here's the answer." A draft says "here's where we're headed — tell me if I've got it wrong." Only one of those invites the conversation you actually need — and drives successful collaborations and outcomes.

Sarah Aylward, Founder & Chief Strategist, Storyworthy

How We Actually Work

The instinct comes straight from design thinking and systems design, disciplines built on showing rough work early and often — sketches before screens, wireframes before code, prototypes before product. The point of a prototype was never to impress anyone. It was to be wrong cheaply, in front of the people who can tell you so.

So we share drafts — outlines, rough cuts, half-built strategies — with our client partners long before they're polished. Not once, at the big reveal, but continuously. Every draft is a small checkpoint: are we still pointed at the right thing? When the answer is yes, we keep moving with real confidence. When it's no, we've lost a day, not a quarter.

Polish Hides the Disagreement

Here's the mechanism underneath it. Polish is a signal — it tells whoever's looking that this is decided. And people are reluctant to reopen something that looks decided. They'll swallow a small doubt rather than ask you to rebuild a beautiful slide. So the polish you added to look professional becomes the exact thing that buries the feedback you needed.

Rough work does the reverse. A hand-drawn flow, a bulleted outline, a strategy with visible gaps — it reads as in progress, which is an open invitation. People point at rough work. They argue with it. They fix it alongside you. The unfinished edges are exactly where collaboration happens.

The Risk Is Backwards

Showing rough work feels risky. You worry it looks unprofessional, that the client will think you're not far enough along, that visible seams undermine their confidence in you. That fear is real — and it's pointed the wrong way.

The actual risk runs the other direction: spending weeks perfecting the wrong thing, then defending it because it's too late and too expensive to change. Polished-and-wrong is the failure mode that costs a quarter. Rough-and-redirected costs a conversation. We'll take the conversation every time.

The move that feels risky — showing your work before it's done — is the safe one. The move that feels safe — the big polished reveal — is where projects quietly go wrong.

Sarah Aylward, Founder & Chief Strategist, Storyworthy

Why Showing Early Drafts Often Actually Delivers

Working this way isn't just philosophically tidy. It pays, in four concrete ways:

  • We get to finished faster. Every early draft kills a wrong turn before we've invested in it. Course corrections happen in hours, not weeks — so the finished work arrives sooner.
  • We stay on budget. The most expensive line item in any engagement is the rework nobody saw coming. Drafts surface misalignment while it's still cheap to fix, which keeps the project on its numbers.
  • We build trust. Letting a client see the messy middle is an act of confidence, not weakness. It tells them we're not hiding the process — we're inviting them into it.
  • We collaborate for real. Work shaped together, in the open, belongs to everyone in the room. Our client partners aren't an audience for the final answer; they're co-authors of it.

How to Show a Draft

None of this works if "rough" reads as "careless." The skill is in how you frame the unfinished work, not whether you hide it. A few things we do every time:

  • Name the ask. Say exactly what kind of feedback you want — "react to the structure, ignore the wording" — so no one wastes energy proofreading a sketch.
  • Mark what's load-bearing. Flag which parts are real decisions and which are placeholders, so the conversation lands where it actually matters.
  • Show the thinking, not just the output. A draft with its reasoning visible is easy to engage with; a mystery half-thing is not.
  • Make it clearly a draft. Rough on purpose — an outline, a sketch, an obvious working title — signals "in progress" and gives everyone permission to push.

Done right, the draft isn't a lesser version of the finished work. It's the thing that makes the finished work good — and makes sure it's the right work in the first place. The polished deliverable still comes. It just arrives at the end of a conversation, instead of standing in for one.

Don't save your thinking for the reveal. Share it while it's still rough enough to change.

Sarah Aylward, Founder & Chief Strategist, Storyworthy