Discovery Workshops

A tool which allows us to determine who should participate in the workshop. The selected participants are not only decision-makers, but also stakeholders if it is possible. Mapping is conducted a few days before the planned workshop, which makes it possible to adjust the workshop schedule to the work schedule of the participants as early as possible.

It is common that we only have a general vision, not a concrete one. We apply the Lean Model Canvas to learn more about your business. It allows us to gain a business perspective of the target users and of the potential methods of investment monetization. Eventually we are able to summarize our insights as a one-page business plan.

This tool makes it possible to translate the product vision into concrete principles. It addresses the issue of the target user and their needs and will allow you to realize which business goals the users of your product want to achieve.

For any business to bring benefits, the end user should be the centre of attention. The user persona tool allows us to realize who and how users will utilize your product. This in turn makes it possible to identify the inconsistencies of the target group and arrange all the information in the form of clear sheets. What's more, we will make sure that the functionalities planned for the further stages of the project will be aimed at the right target users.

This stage of the workshop involves describing the behavior of product users in the form of stories. The descriptions are grouped according to functionality, so that the initial structure of the product is laid out right ahead of you. This is a quick and inexpensive form of acquiring a requirement list to develop an application that gives priority to user needs.

This method involves describing and labelling the collected functionalities as must have, should have, won’t have and could have, both from a user and business perspective, to be implemented in the project. This will help you avoid the "featurists" effect, i.e. emphasizing functionality instead of value. During this stage, our expert (together with your team) streamlines the product into MVP and applies percentage budget trimming to simulate the selection of the key functionalities. As a result, you receive a detailed implementation plan and build awareness of such functionalities that do not directly offer value for the user.

Having collected a lot of detailed information about your business and product, we analyze it in terms of completion risk. We mark key stages of the development cycle which may lead to problems with the application’s completion. By doing so we want to avoid problems at the early stages which may lead to development delays or financial issues.

A Lo-Fi Prototypee (which stands for ‚low fidelity’) is a tool that enables you to quickly visualize your product as an interactive mockup. We do not focus on colors at this stage. The most important task is to present all the agreed functionalities and show how the application will work. The mockup may be used as a tool for testing user needs.

Having collected detailed information about your business and product, we are able to estimate the cost of the application. Such estimation is of a non-binding nature and its key purpose is to demonstrate the project’s value based on specific conclusions and decisions. If you decide to compare our offer with competing ones on the market, you will be sure that the differences in pricing do not result from the low quality of the project brief and its accuracy level will be much higher than in the case of a simple application description.

If the vision of your project is much more complex, we can additionally utilize two other tools, which will allow you to gain further insights on top of the basic process.

This tool is used to verify the validity of your business idea among target users or in a company. These are prototype versions of the project, built to show the possibilities and benefits of the future solution. Our task is to present the business results of a given idea in an environment as close to the production environment as possible.

A comprehensive tool used to create structurally complex and much more complicated information systems. It is also applied in process-based solutions. We utilize it to jointly understand the complexity of requirements, internal mechanisms, chronology of events, the process and user permissions, all in order to properly map functionalities and establish accurate application architecture. This tool will allow you to thoroughly understand the user process in the application and identify those process areas that need to be optimized.