In this interview, our UX/UI expert Gundars delves into the general awareness and demand for PoC, common misconceptions, challenges in development, the impact of emerging technologies, and future trends.
This discussion offers valuable insights and practical advice for both seasoned IT professionals and business leaders new to PoC.
Join us as we explore how proof of concept can lead the way in helping businesses optimize processes, navigate uncertainties, and achieve their goals efficiently through PoC.
Q: How often do businesses ask for a proof of concept, and are they generally knowledgeable about it?
A: Lately, the demand for this service has increased, particularly among larger companies with advanced knowledge of IT processes and PoCs. In such cases, PoCs are often presented to the board to secure larger funding for specific projects.
Businesses with less experience are usually new to this concept but generally appreciate it as it allows them to start a project without long-term commitment. This approach helps them save money and better define their budget, needs, and goals.
Q: What are some common misconceptions businesses have about proof of concept?
A: Clients with less experience often don't realize that it's possible to create a functional prototype that test users can interact with, without significant coding and development costs.
Additionally, some clients may be unaware of the significant time difference between making changes during the design prototype phase (PoC) versus the development phase. We can easily make 10+ iterations in the PoC phase, while in the development phase, each major change is slow and costly.
Another misconception is that PoC might seem like an extra step. However, even if we start developing the project immediately, we typically begin with a design prototype. It's more effective to provide estimates, select technologies, and set a timeline after the prototypes are done, rather than before.
Q: Which industries benefit the most from developing a proof of concept, and why?
A: Generally, all industries can benefit from developing a proof of concept. PoC is particularly valuable in projects with many unknowns, as it provides all involved parties with an understanding of what to expect and how to achieve it. It's highly beneficial for projects where the best approach is still being determined, as iterative prototyping, testing, and improving are essential.
This is less relevant if the processes are well-known, there is a previous version of the solution, and feedback and data have been collected. In such cases, the process is better known, easier to explain to developers, and there are fewer risks of fundamental changes. If the client is confident about the precise technical and functional solution, and everyone involved understands it, a PoC is less crucial, and development can start right away.
Q: What are some of the biggest challenges you face when developing a proof of concept for a client?
A: The biggest challenges typically arise when multiple third-party solutions are involved, as there are uncertainties about their technical capabilities. Questions about APIs, data availability, and more can pose significant challenges.
However, addressing these challenges early allows everyone to understand technical capabilities, choose the best technology, and determine if additional infrastructure changes are necessary to achieve project goals.
Q: What factors contribute to the success of a proof of concept?
A: One of the most important factors is involvement from all parties. It's crucial that all sides—end users, business, and the technical department—are engaged in the process to reach the optimal solution.
Communication is key, and it's better for issues to arise early so that major changes can be made sooner, saving time in the long run.
Q: How long does it typically take to develop a proof of concept, and what resources are required?
A: The time frame depends on the scale of the project, but typically, we can get an idea of the project's scope and functional direction within a couple of weeks.
Q: Can you share any memorable experiences or insights from past PoC projects, without mentioning specific details?
A: Recently we developed an ESG platform where PoC was a crucial part of the project as the whole industry is very new and there aren't many products with previous experience in this field so we had a lot of testing and experimenting to do. We studied the legal requirements and worked together with our potential customers who already had some manual ESG reporting processes in their companies. As we made the first prototypes, we were able to do some user testing with real potential users, validate our ideas, add desired additions from them, and confirm the relevance and necessity of the product in general. After showcasing PoC we saw a lot of interest from potential customers and even were able to sell the product in advance. Therefore we could involve actual future platform users in the development process giving them some control in product development and assuring that the product meets the end user's needs. After a lot of iterations, testing, and discussions we could develop the platform's first version, choose the appropriate technology, and move fast with development as we had a general concept of the platform. Now we continue improvements in cooperation with the customers and make new PoC's for new platform features that we can validate with end users.
*To view a prototype in action, please refer to the additional information provided at the end of this blog post.
Q: What advice would you give to businesses considering a proof of concept for their next project?
A: Start small. If you are unfamiliar with the process, begin with a main feature MVP, go through user testing, gather insights and feedback, and understand the process.
This approach reduces the risk of wasting a large budget on a large-scale project. You can always introduce new features, and your priorities may shift during the process. This is an agile process, so let the results and feedback guide you.
Q: How has the approach to proof of concept evolved over the years at Mitigate?
A: Currently, PoC is the first step in any Mitigate project. Projects start with an idea, which becomes a concept that we test to get the best results. Even if we are certain about developing a specific feature, we still need to figure out the best approach and assess risks. Many great tools have evolved over time, allowing us to test concepts in more realistic environments and obtain precise data and feedback.
Q: How are emerging technologies, such as AI and IoT, influencing the development and outcomes of proofs of concept?
A: AI can now assist with content generation for different project aspects, reducing the amount of work required to create a prototype while providing a near-end-product feel. Some AI tools may eventually help with PoC creation or suggest potential solutions to explore.
Q: How involved are clients typically in the development of a proof of concept, and how does their involvement impact the process?
A: Clients are typically very involved in the PoC process. We conduct regular meetings, with potential solutions being discussed internally and aligned with business and end-user needs.
Depending on the client's technical knowledge and skills, we try to involve them as much as possible. Transparency is important, and it helps everyone understand the process and the potential future product better.
Q: How do you customize your proof of concept approach to fit the unique needs of different clients and projects?
A: Each project is unique, so we begin with client and user interviews, research, and surveys to understand the specific approach required. It's important to understand the end-user needs and project goals in order to tailor the PoC accordingly.
Q: Lastly, what future trends do you foresee in the field of proof of concept development, and how is Mitigate preparing to adapt to these changes?
A: As technologies evolve, we find more efficient ways to create and validate PoCs. AI plays a significant role in many fields, and we constantly test the limits of new technologies, trying to implement them in our latest projects.
While some technologies are not yet fully ready to take over some processes, we gradually implement more features to save time and make the process quicker and more affordable. Many clients share our enthusiasm for new technologies and agree to test new solutions, providing valuable learning experiences.
If any of the topics related to proof of concept have sparked your imagination or curiosity, we are more than happy to answer all your questions or discuss a potential collaboration.
Feel free to contact us for a non-binding conversation and let's bring your projects to life, all the while minimizing risk and scaling its potential.
