Proofs of concepts is a discipline that the CTO has in providing the organization quick and broadly implemented ideas that helps the stakeholders make decisions. It is the dollar bills we throw at a problem before we commit the big bucks. The CTO is shrewd in finding the problem behind the problem and then provides a super-focused prototype to bring concepts to life so that speculation and hand waving can go away.
Get into a rhythm of producing concepts, even when there isn’t a major compelling business problem that needs to be solved. Even minor initiatives, when features aren’t clear, can benefit from first building a concept.
A Concept is “evidence, typically derived from an experiment or pilot project, which demonstrates that a design concept, business proposal, etc., is feasible.” ~ Oxford Dictionary.
Business teams, prospects, and customers are acutely aware of the problems that they are facing (which they hope the product can solve), however they are often less able to visualize the solutions. Concepts, or proofs of concepts (PoC), bring our imagination to life. The goal with Concepts is to seed people’s minds with examples. When the CTO creates a concept, it will be able to reduce the amount of energy people need to use in order to imagine the technical solution.
Business teams are often more interested in what a technology can do, rather than how it works. Frame discussions around the benefits a technical product or idea can bring to the business, such as cost savings, improved efficiency, or new capabilities. Avoid jargon and technical terms when possible. Instead, use simple language and analogies that the business team can understand. Remember, the aim is to convey the core ideas and not to teach them how to build or code a product.
Our concepts need to show how the problem they are having could be tackled with a product solution. As technologists we often have the urge to build the complete solution, but concepts are almost always a facade. Concepts are implemented to convey an idea, not to implement the solution. We can convey an idea many ways:
By telling a story about how the technology will be used, what problems it will solve, and how it will improve the business, you can make the technical details more interesting and relevant. Be patient with non-technical team members and encourage them to ask questions. This will help ensure everyone has a clear understanding of the concept and can help you gauge what areas need further clarification.
Want to learn more about the difference among Concept, Prototypes, MVP and Production Product? See the MVP block.
Creating a concept instead of jumping straight into building the full solution has several advantages. Here are a few key reasons: