A collection of practical tools, frameworks, and articles on the business of turning ideas into something real. Aimed at teams working without specialist innovation departments or large budgets.
The Idea Lab is Falogino's resource centre. It exists because the programme sessions can only cover so much ground, and because the questions teams ask most often tend to be the same ones regardless of sector or company size. This page gathers thinking on those questions in one place.
The content here is practical rather than theoretical. Where we reference a framework, we explain how to apply it. Where we discuss a challenge, we describe what has actually helped in real situations. Nothing here requires specialist knowledge to understand or apply.
Every idea rests on assumptions about what customers want, how they behave, or what is technically possible. The assumption map is a simple exercise that surfaces those assumptions and ranks them by how critical they are to the idea's success and how little you currently know about them. Start with the high-criticality, low-knowledge assumptions. Those are the ones worth testing first.
When teams hear the word prototype, they often imagine something polished. This framework deliberately reframes the goal. A five-minute prototype is the roughest possible representation of your idea that still communicates the core concept to another person. It could be a hand-drawn sketch, a verbal description read aloud, or a single slide with a headline and three bullet points. The goal is to make the idea visible, not impressive.
Getting useful feedback on an idea is harder than it sounds. People tend to be polite, especially with colleagues or when they sense the idea belongs to someone with authority. This guide covers the framing, question structure, and listening techniques that make concept testing conversations more productive. The key principle: your job in the conversation is to listen, not to explain.
An idea that has been discussed multiple times without moving forward is not necessarily a bad idea. It might be stuck for a specific, identifiable reason. This decision tree walks through the most common reasons ideas stall and points toward the appropriate next action for each. Sometimes the answer is to test a specific assumption. Sometimes it is to reframe the idea entirely. Occasionally it is to set it aside without guilt and focus elsewhere.
Deferring an idea without a clear mechanism for revisiting it is functionally the same as dismissing it. Most teams have a graveyard of ideas that were "parked" and never retrieved. Here is what a genuine holding system looks like and why it matters.
One of the most persistent misconceptions about rapid prototyping is that the prototype needs to resemble the final product. It does not. What it needs to do is answer a question. Understanding that distinction changes what you build and how you build it.
In concept testing conversations, the absence of negative feedback is not the same as positive feedback. People are socially conditioned to be encouraging. This piece looks at the specific signals that indicate genuine interest versus polite support, and how to design conversations that surface the difference.
One of the most common objections to building an experimentation practice is that there is no time. This is often true. But the question is not whether to find large blocks of time, it is whether to find small, consistent ones. The difference in outcomes is significant.
The full programme involves four sessions ranging from half a day to a full day each. Between sessions, we encourage small experiments that typically take two to three hours per week. The programme is designed to fit around existing commitments rather than replace them.
No. The programme is designed for people who work with ideas in the course of their normal job, not for professional innovators or designers. The methods are deliberately accessible and require no specialist background.
Yes. Several of the most effective runs of the programme have been with small teams. The minimum useful group size is around four, though some modules can be adapted for smaller groups if needed.
Module four specifically addresses this. Participants leave with a lightweight rhythm for continuing the practice independently. We also offer optional follow-up sessions at one and three months for teams that want additional support during the embedding period.
The programme is designed for teams that do not have a dedicated innovation function. However, it has also been used by organisations with innovation teams to spread the capability more broadly across the business, so that idea development is not bottlenecked through a single department.
The contact page is the right place to ask. We are happy to discuss specific situations and whether the programme is a good fit before any decisions are made.
No pressure, no obligation.