Our discovery: starting with strategy to deliver value

Our experience in mobile and web development has convinced us that being excellent technical executors of our clients’ requirements is not enough to deliver value.

With our Money back contract mode, we have given the clients the possibility to have constant decision-making power over the project, instead of tying them to initial choices that can “force” them into an outdated scenario. And we give the same possibility to the users as well, we can listen to their feedback and adapt the solution, be it mobile or web.
This approach makes it possible to change course or stop before the completion of the plan initially envisaged: it frequently happens that when faced with an articulated plan, only certain parts turn out to be really necessary for the end user.
So don’t panic: you can change the stages towards your goal, and change the goal too.

We have been adding an initial phase – discovery – to our contract, a work session lasting from one day to two, in which our team works together with the client’s team to:

  • explore together the project’s vision, business objectives and application scenarios, to create alignment, avoid misunderstandings and take nothing for granted, and allow all stakeholders the opportunity to bring their input.
  • and converge towards a solution co-created by all the necessary expertise (domain, strategic, technological). And value-driven, clearly identifying what is the “value to be delivered to whom” and then thinking about project features.

How does it work in practice?

The working session goes through four main stages:

  • presentation of the idea, goals and actors in the process. With this information, we decide to go deeper into the business idea to explain all its implications (using for example tools such as Lego Serious Play™ or the business model canvas) and/or to analyse alternative scenarios to bring out threats and opportunities (swot analysis).
  • against what emerges, we define or collect useful information for the project, such as a detailed profile of the users of the software, any project constraints or metrics indicating the achievement of objectives.
  • we trace the flow of software use (often using the event storming technique) to the point of creating user stories, prioritising them and identifying an mvp or releases.
  • we define the areas of intervention in the project development, both ours and the client’s, if they are involved in the development of the solution with us. Up to agreeing rituals and tools to be used with the client during the project, to communicate effectively and be aligned.

What are the main advantages?

  • start the project with the main objective of delivering value to the client and its end user.
  • produce quality information, essential to make estimates as reliable as possible, while remaining estimates.
  • be in a position to make the right decisions during the course of the project. the alignment generated by this session allows those working on the project to do so to the best of their ability, without the uncertainties that are generated in those who have a partial view of the project.

If the contract allows us to change the route or even the destination during the course of the project, with discovery we ensure that the destination is clear to the whole team. This makes easier and faster to reach it.