Flash It is a rapid concept communication technique in which a designer presents a rough idea — a sketch, a photograph, a paragraph, or a prop — to a colleague or potential user for a very brief 'flash' of exposure, then asks for an immediate, unfiltered reaction. It is faster and less formal than a review session and less resource-intensive than a usability test: it is a thirty-second conversation that can happen in a corridor, at a desk, or via a shared photo. The brevity is what makes it valuable — the reaction captures first impression, not constructed opinion.
What It Is
Flash It is less a formal method than a design habit: the practice of showing ideas to other people at the earliest possible stage, before they have been polished or elaborated. It produces two things simultaneously — quick feedback on whether an idea communicates clearly, and the social accountability of having made an idea visible that often motivates further development. Its informality is deliberate: the lower the stakes of sharing an idea, the earlier teams will share them and the more iterations become possible.
How to Run It
- Draw, photograph, or write a rough representation of the idea you want to Flash.
- Find a colleague, user, or stakeholder and show it to them for five to fifteen seconds.
- Ask one question: 'What do you think this is?' or 'What would you use this for?'
- Capture the response in a single sentence before elaborating or explaining the idea.
- Compare the response to your intent: does their interpretation match what you meant?
- Iterate the idea based on the gap between intent and interpretation, then Flash again.
When to Use It
Flash It is most useful as a constant practice throughout the design process — a way of shortening feedback loops to the minimum viable interval. It is particularly effective for individual designers working alone who need external perspectives to challenge their assumptions, for design teams who tend to hold ideas too long before showing them externally, and for moments in a design sprint when time pressure makes formal review impossible.
Tips for Success
- Do not explain the idea before showing it: the explanation will shape the reaction and corrupt the first-impression data.
- Flash to people outside the project team: colleagues who know the context cannot give you uncontaminated first impressions.
- Build Flash It into your daily design routine: five Flash sessions per day produces more learning than one formal review per week.
- Document Flash responses systematically over time: patterns across many brief reactions are more reliable than any single considered critique.
