From requirement to sketch: How to use low-fidelity design to drive better conversations
There’s a moment every Business Analyst encounters at some point in their early career, and I felt it ealry on — it’s usually during a workshop, usually when everyone is staring at you:
“…okay, but what does that actually look like?”
It’s rarely said with frustration.
It’s usually said with hope.
Language alone can only take you so far. This is where low‑fidelity design becomes one of the most powerful tools in your BA toolkit. Not Figma. Not fancy UI kits. Not pixel‑perfect screens.
Just a rough sketch.
On a page.
In a notebook.
On a whiteboard.
On a napkin if you need to.
Because the goal isn’t beauty.
The goal is shared understanding.
In this article, I want to show you why low‑fidelity sketching works, how rough is “rough enough”, and why sketching is one of the fastest ways to reduce ambiguity, build alignment, and accelerate decision‑making — even if you don’t see yourself as “a designer”.
And this is the moment where many early‑career BAs panic, because they associate “showing” something with producing a polished wireframe, or a screen in Figma, or a fancy workflow diagram they’re afraid they’ll get wrong.
But here’s the truth I try to teach through The BA Project:
You don’t need to be a designer. You just need to sketch.
Not beautifully.
Not perfectly.
Not with the right icons or pixel alignment.
Just enough to bring clarity to the conversation.
Why sketching Is so powerful for BAs
Business Analysts live in the space between ideas and delivery.
We translate.
We clarify.
We make sense of the messy middle.
Sketching amplifies all of that — because it gives shape to ideas before they become expensive.
Here are the big reasons sketching works:
1. People think visually, even when they’re not visual people
When you sketch, you give stakeholders something concrete to react to. You’re no longer asking them to imagine a concept — you’re asking them to respond to something real enough to discuss, but safe enough to change.
2. Sketches remove the fear of getting it wrong
If you open Figma, people assume you’re showing a final design. If you sketch on paper, everyone knows it’s early‑stage — which means:
they critique the idea, not the polish
they contribute freely
they feel part of the solution, not judged by it
3. Sketching is fast — which makes it cheap
You can sketch five versions of a screen in five minutes. You cannot do that in any digital tool without introducing subconscious “precision”. Sketches help you explore the idea without committing to the idea.
4. It cuts through ambiguity like nothing else
Words like “dashboard”, “summary page”, “workflow”, “task list”, “form”, “quick action” — all of these mean different things to different stakeholders. A sketch means everyone is finally talking about the same thing.
How Rough Is “Rough Enough”?
There’s a golden rule I tell junior, new, or aspiring BAs:
If your sketch looks tidy, you spent too long on it.
Low‑fidelity design should look like a draft — because drafts invite conversation.
Here’s what good low‑fi usually looks like:
boxes instead of components
squiggles instead of text
placeholders instead of labels
arrows instead of complex flows
stick figures instead of personas
grey blobs instead of images
You are not trying to show:
“How it will look”
You are trying to show:
“What goes where, and why”
| Fidelity Level | Description |
|---|---|
| Lo-Fi | Boxes, arrows, squiggles, placeholders — fast and disposable |
| Mid-Fi | Structure is clear, layout stable, still no styling or branding |
| Hi-Fi | Visual design, real content, interactions — usually owned by UX, or assigned 'Design' resoruce |
How sketches reduce ambiguity and accelerate agreement
Here’s the real magic. Sketches don’t just show ideas — they reveal gaps. When you sketch a workflow or screen, questions surface immediately:
“Where does the user go next?”
“What happens if they skip this field?”
“Should this be a button or a link?”
“Do we even need this step?”
In other words, sketching exposes the decisions nobody realised they were making. This is why low‑fi design is often more valuable than high‑fi. It’s messy enough to spark thinking. It’s imperfect enough to invite challenge. And this makes your workshops sharper, faster, and genuinely more collaborative.
Here are the three big accelerators:
1. Faster alignment
Once you sketch, stakeholders stop using vague phrases.
They point.
They react.
They get specific.
2. Earlier risk detection
You catch workflow issues before they hit development.
You reveal assumptions before they become dependencies.
3. Higher-quality requirements
Low‑fi design ties everything together:
user stories
acceptance criteria
data needs
business rules
edge cases
But I’m not a designer…” - Good.
You don’t need design training to sketch. In fact, your lack of design training is an advantage.
Why?
Because low‑fi sketching is about clarity, not craft. Stakeholders don’t want you to be a designer. They want you to help them see what they mean. You can do that with a pen and paper. You can do that with a Sharpie on a whiteboard. You can do that without opening a single design tool.
The Easiest Way to Start: 5‑Minute Sketching Loop
Lo‑fidelity sketching isn’t about drawing well — it’s about thinking clearly, together. The moment you aim for neatness or completeness, you stop exploring and start defending ideas. This approach deliberately keeps things rough, fast, and a little uncomfortable, because that’s where the real conversations happen.
By sketching multiple versions of the same idea, you create space for comparison instead of premature agreement. By circling what feels unclear, you turn uncertainty into a productive input rather than something to be avoided. And by showing just one version to stakeholders, you anchor the discussion without overwhelming it — allowing the solution to emerge collaboratively, in the room.
Crucially, the sketch itself is never the output. The value sits in the conversation it enables. Capturing feedback without refining the artefact keeps everyone focused on intent, outcomes, and trade‑offs — not visual polish. Only once that shared understanding is reached do you translate the discussion into something more formal: user stories, flows, and acceptance criteria.
It’s a simple discipline, but a powerful one. Done well, it shifts teams out of solution mode and into sense‑making mode — which is exactly where good analysis belongs.
| Step | What To Do (and Why) |
|---|---|
| Draw three versions of the same idea | Fast sketches of the same concept. Don’t overthink it — the goal is exploration, not perfection. |
| Circle the parts that feel unclear | These become your workshop questions and discussion prompts. |
| Show just one version to stakeholders | Use a single sketch to focus the conversation, then iterate live together. |
| Capture feedback — don’t refine the sketch | This prevents the conversation drifting into hi‑fi thinking too early. |
| Translate the final conversation into requirements | Turn outcomes into user stories, flows, and acceptance criteria. Simple — but transformative. |
Low‑fidelity prototype (sketch level)
Low‑fidelity prototypes are the fastest, most forgiving way to bring an idea to life — and they remain one of the most underrated tools in a BA’s skillset. At this level, the goal isn’t aesthetics or accuracy. It’s clarity.
A sketch strips away everything except the essentials: layout, flow, and intent. When you sketch, you’re not designing a UI — you’re externalising your thinking so that others can see what you mean without making assumptions.
This level of fidelity shines in early conversations where ambiguity is high and direction is still forming. Because sketches look unfinished, stakeholders feel safe challenging them. They add, erase, push back, and co‑create with you. And that’s the point.
A lo‑fi sketch isn’t a deliverable — it’s a conversation starter. It gives teams a shared picture before any effort is invested, allowing problems, gaps, and misalignments to surface early when they are still cheap to fix. Low‑fi also helps overcome “blank page paralysis.” Once something is on the page — even a rough outline — momentum builds. The discussion becomes more concrete. Decisions become easier. And the risk of everyone imagining different things begin to disappear.
Mid‑fidelity prototype (wireframe level)
Mid‑fidelity prototypes take the raw thinking from the sketch stage and give it structure. Think of this as the architectural drawing version of your concept: still simple, still free of branding or polish, but clear enough that people can react meaningfully to layout, hierarchy, and functionality.
At this level, your design decisions become more intentional. You’re beginning to define spacing, page structure, navigation placement, and content blocks. You’re moving from “what goes where” into “how the user will move through this.” It’s the point where your prototype becomes a tool for validating flows, checking logic, and spotting friction points.
Mid‑fi wireframes are especially useful for aligning with UX designers, developers, and Product Owners. They help everyone confirm the feasibility of what’s being proposed without the distraction of colours, typography, or visual styling. It’s a safe zone where feedback is still easy and expectations are still flexible — yet the clarity is high enough that teams can proceed confidently into more detailed design.
This is also the fidelity level where BA work aligns beautifully with design practices. You take conceptual requirements and translate them into interaction patterns that users will eventually experience. It’s still lightweight — but purposeful.
High‑fidelity prototype (branded UI level)
High‑fidelity prototypes are your near‑final vision: fully branded, styled, and presented with enough detail to feel real. At this level, the design isn’t just describing functionality — it’s demonstrating what users will actually engage with. It communicates tone, personality, and intention. The typography, colour palette, spacing, and visual hierarchy all reinforce the brand and the experience you want users to have.
For BAs, high‑fi prototypes are powerful because they bring every earlier conversation into sharp focus. Abstract ideas become tangible. Stakeholders can almost feel themselves using the product. Feedback becomes more emotional — which is often exactly what you need when preparing for user testing, leadership review, or delivery handover.
High‑fi prototypes reduce risk dramatically. They expose gaps that weren’t obvious in wireframes (such as long labels, missing states, complex interactions), and they highlight where visual design impacts comprehension. They also help delivery teams make more accurate estimates because the visual intent is no longer hypothetical — it’s explicit. In short, high‑fi prototypes are where strategy, design, and requirements converge into a single, coherent representation of the intended experience. They move the conversation from “what could this be?” to “this is what we’re building.”
Final Thought: Sketching is a facilitation superpower - not a design skill
Low‑fidelity design isn’t about how well you draw. It’s about how clearly you help people think. When you sketch, you:
reduce risk
speed up alignment
expose assumptions
strengthen relationships
build confidence (yours and theirs)
and create better requirements, faster
If you’re an aspiring BA, or someone switching into the field, this is one of the most empowering skills you can build - because it levels the playing field. You don’t need the perfect tool.
You need the willingness to draw the first box.
