Over the course of about 15 years between consulting and academic life, I have been working – and teaching – with new business projects, many of them innovative. In the meantime, I used the traditional Business Plan, then the Business Model Canvas, which I met in 2010, and since then I have used several other tools, such as Empathy Map (which is already in version 6.0), Value Proposition Canvas (which was called Customer-Value Canvas in its early versions), Lean Canvas (one of the first variants of BMC); BASE Board (one of my favorite tools) and many others – I’m going to make a post soon just about it – in addition to various strategies and methodologies – like Silly Cow Challenge, for creativity; Wall of Ideas (which I work in a different way from the one presented in Design a Better Business); Battle of Concepts; Buy a Feature; Co-creation; Storytelling; Pitch; and others.
There is no such thing as a perfect tool in business. The ideal, in fact, is a combination of tools and strategies, tailoring them to every reality (training, real work, consulting) and the target audience. At least that’s what I’ve done.
I’ve also been testing some other possibilities and strategies, as well as drawing some tools. The Battle of Concepts, for example, is one of the techniques that brings better results when working with different groups in the classroom to provide a quality leap in project ideas.
But it was Problems & Solutions, another activity I drew that gave rise to my first public tool in 2017: The Business Idea Canvas (actually, it’s not the first – before that, there are already 2 versions of Cut the Crap Canvas, but I still do not consider it in point to share).
The Business Idea Canvas v 1.0
The tool aims to be one of the first stages of the process of ideation, while doing a check on the problem that is being worked on. I understand that, often, the “problem” to be solved is not, in fact, a problem. I.e.: a recent project that would function as a platform to find friends to play football. This is not a problem – at least in Brazil lol. Usually, the real problem is to make it a priority so that there is room in the agenda for this practice.
In other cases, there is a complete misunderstanding of what the problem really is. Ex: heavy traffic in a big city is not the problem itself, but the result of some other problems (living far away, for example, or a poor transport infrastructure). It can also be the cause of various problems, such as being late for work or some commitment.
There is still a third situation, when it is expected that a particular public wants a solution that, in fact, they do not want. Ex: queues to enter a nightclub are actually attractive to a nightclub, so the owner would not have much interest in solving it. Seeking to deal with situations such as these, in this context, that The Business Idea Canvas was born.
You can start working from the idea (Proposed Solution, central block) or Problem (first block from the left). Personally, I believe it makes more sense to deal with the problem, but there is no restriction on that.
This initial block should explain and specify what problem you are trying to solve. Assuming value creation comes from solving some kind of problem, it seems reasonable to start designing the solution from that point on. The definition of the problem may arise from observation or from the data collected on the Empathy Map, which may work together with the BIC.
Thus, this block seeks to understand what is, in fact, the problem: its causes, origins, effects, implications.
The delineation of the affected public can also be obtained in conjunction with the Empathy Map.
Thus, it is important to know who is directly affected by the problem and in what way. How many are these people? Where are they?
From this block, the Empathy Map no longer helps us and we need to delve deeper into the problem to understand some of its nuances. Besides those directly affected, who else suffers the impact of this problem? Relatives, friends, other stakeholders? This information can help us determine sales strategies, communications, and more clearly define what should be central to the solution and what is secondary but important.
Vampires are usually ignored people when designing a solution proposal, but they are able to undermine the chances of business success. They are those stakeholders who, somehow, benefit from the existence of the problem, as in the case of the dance club queue. So, is it important to know who benefits from the existence of this problem and possibly act against the solution?
I think this is a big blind spot in most of the initial business modeling and building tools.
Nowadays, it is difficult to say that a problem is not solved, partially solved or even treated in a palliative way. It is virtually certain that currently this issue is resolved in some way, although palliative way. I.e .: Someone who suffers from flooding probably installed a gate to function as a deck in front of the house; or another case, an incurable disease whose symptoms are treated with a cocktail of remedies.
It is very unlikely that anything has even been attempted to solve the identified problem. So how do affected people deal with this problem today?
NOW, HOW MUCH?
The current solution, even if it is palliative, represents some kind of cost to the affected public. How much does it currently cost to solve – or at least threaten – this problem?
It is necessary to take into account that the client, when considering adopting the proposed solution, will compare it against the current alternatives in terms of costs and offered benefits. This relationship needs to be positive in some way so the customer may consider your proposal.
TREND & PATTERN
The last two blocks outside the central block will give the first clues about the proposed solution.
In the TREND block, the business analyst should point out to which trend (global, local, social, technological) this problem (and a possible solution) belongs. This indicator will be important when assessing the future potential of the business idea.
In turn, the PATTERN block is directly related to the solution that will be proposed (and, therefore, can be filled after the proposal). This block relates to which business pattern, which archetype of business model known to this proposal aligns. It serves to facilitate the understanding of the solution proposed from an analogy of a known model. I.: the Uber of the painters of house; the professions Tinder; the AirBnB of the boats.
The solution block is the most important and will provide the basis for migrating the work to tools more focused on Business Models (such as BMC, BASE Board, Lean Canvas, etc.), but it can only be built after a clear understanding of the problem, its costs, those affected by the problem, and those who benefit from it. After this understanding, the business analyst or the entrepreneur can begin to propose a solution that is appropriate to the problem.
Once the solution (or solutions) is proposed, the tool allows to indicate the level of the proposed innovation (DISRUPTIVE or INCREMENTAL) and the focus of this innovation (PRODUCT, PROCESS, MARKET and/or BUSINESS MODEL). These elements will also facilitate understanding of the technical and market feasibility of the solution.
LAST, BUT NOT LEAST
The tool aims to be one of the first steps in the process of ideation, while taking a deeper approach to the problem being worked on. It is not a tool for building business models, although it is a very useful support tool in the early stages of construction. In addition, because it is part of an iterative process, one can go back to it and reconfigure the proposal according to the progress of the project and as new relevant data emerge in the context of the innovation in question.
In order to facilitate the understanding, I set up a commented example of the application of the tool in this post.
This is the first public version of this tool and I would be very happy to receive feedback on the application of the tool in other contexts and practical cases.
PS: The Battle of Concepts, Problems & Solutions, Wall of Ideas tools and methods cited in this text, and other strategies I use for designing innovative businesses will be presented over the coming weeks.