Put the Sticky Note Down: Why Your Best Ideas Come from a Biro and the Back of an Envelope

Let's talk about friction. Not the bad kind — not the friction of a broken build pipeline or a client who keeps changing the brief on a Friday afternoon. The good kind. The productive, uncomfortable, brain-engaging kind that happens when you're forced to think something through without a template to fall back on.

British tech has spent the last decade systematically eliminating this friction. And in doing so, it may have accidentally engineered away the conditions that produce good ideas in the first place.

The Tool Stack That Ate the Thinking

Here is a partial inventory of the collaboration infrastructure a mid-size British software team might reasonably be expected to maintain in 2024: Miro for virtual whiteboards. Figma for design. Notion for documentation. Confluence for the documentation nobody reads. Linear for task tracking. Slack for communication. Loom for the video messages nobody watches. And approximately four other tools whose free trials were started by someone who left the company eight months ago and whose subscriptions are still being quietly charged to the company card.

Each of these tools exists to solve a real problem. Several of them solve those problems rather well. The issue isn't the tools themselves — it's what happens to thinking when every stage of the problem-solving process has a designated digital environment with a pre-built structure.

You open Miro and there's a template. You open Figma and there's a component library. You open Notion and there's a doc format. The scaffolding is already there, which means the first cognitive act — the genuinely difficult one, the one where you stare at a blank surface and force your brain to organise itself — has already been done for you. By a product designer in San Francisco who has never met your client, doesn't know your constraints, and has absolutely no idea what problem you're actually trying to solve.

What the Napkin Actually Did

The mythology of the napkin sketch — the idea scrawled over a pint, the architecture diagram on a beermat, the wireframe on the back of a till receipt — is not just nostalgia. There's something cognitively significant happening in those moments, and it's worth taking seriously.

When you draw by hand, you are forced to make decisions. A biro on paper doesn't have an undo button. It doesn't snap to a grid. It doesn't offer you a library of pre-made shapes. You draw a box, and it's a wonky box, and that's fine, because the box is not the point — the relationship between the boxes is the point. The hand-drawn diagram is a thinking tool, not a deliverable. It is allowed to be wrong, incomplete, and covered in crossing-out.

Digital tools, by contrast, carry an implicit pressure towards polish. A Figma mockup that looks finished invites feedback about its appearance rather than its logic. A Miro board with colour-coded sticky notes and a clear visual hierarchy suggests that the thinking has already been done, even when it hasn't. The medium signals completion before the idea is ready.

There's research to support the intuition. Studies in cognitive psychology suggest that the act of drawing — particularly freehand, imprecise drawing — activates different problem-solving modes than typing or clicking. The physical engagement of sketching helps externalise mental models in ways that are genuinely different from digital composition. You're not just recording a thought; you're discovering it.

The Design Sprint Industrial Complex

Somewhere in the mid-2010s, British tech fell hard for the design sprint. Five days, a structured process, Post-it notes on every surface, a prototype by Friday. The Google Ventures methodology swept through product teams like a particularly enthusiastic management consultant, and suddenly every company with a product problem was booking a sprint room and arguing about How Might We statements.

Design sprints are not bad. Done well, they can be genuinely useful for unsticking a team that's been circling the same problem for months. But they have a shadow side that rarely makes it into the case studies: they are expensive, they are process-heavy, and they have a tendency to produce outputs that look like thinking without necessarily being thinking.

The sprint generates artefacts. The artefacts go into a shared drive. The shared drive is consulted periodically and then, gradually, forgotten. Meanwhile, the original problem either gets solved by a developer who found a different approach entirely, or it doesn't get solved at all, and the team books another sprint.

Contrast this with the experience of sitting in a pub in Leeds with a developer and a product manager, a pen, and a genuine problem. No agenda. No timeboxing. No designated roles. Just two people who understand the constraints, arguing about the best approach and drawing increasingly elaborate diagrams on whatever paper is available. This is not a romantic fiction — this is how a significant proportion of Britain's most interesting software products began.

Relearning the Lost Art of Messy Thinking

The good news is that nothing has been permanently lost. The capacity for unmediated, friction-rich thinking is still there — it just needs permission to exist.

Some practical provocations, offered in the spirit of a beermat scrawled in haste:

Start your next problem on paper. Not a whiteboard — paper. Something you can fold, scribble over, and throw away. Give yourself twenty minutes with no tools open. See what comes out.

Declare a Miro-free zone for your next exploratory session. Sit in a room with a whiteboard and markers that are probably running dry. The constraint will irritate you and then, quietly, help you.

Treat the first digital version as the second draft. Whatever you draw by hand is the first draft. Digitise it only when the thinking is done, not while the thinking is happening.

Notice when tools are doing your thinking for you. If you're choosing between template options rather than making a genuine decision, stop. Close the tab. Pick up a pen.

The best ideas this industry has produced were not born in a perfectly facilitated workshop with a designated timekeeper and a Spotify playlist in the background. They were born in the gap between knowing what the problem is and knowing what to do about it — that uncomfortable, productive, irreplaceable space where actual thinking happens.

You don't need a better tool for that. You need a worse one. Preferably one that runs out of ink halfway through and forces you to finish the thought in your head.