Bolunes

Sports betting

Product description

Bolunes is one of the products of the Lunes company. A sports betting application that uses blockchain technology in its financial part, having as its main currency for LUNES.

My Contributions

Product Designer: I was responsible for facilitating a collaborative workshop to align the business, technology and design teams on the redesign of Bolunes.

Project overview

We chose lean inception to create a redesign of an old product that was completely obsolete. The idea was to help align the team to build a new product solution with an innovative redesigner, reshaping the user experience in the app.

Duration

1 Week of workshop

Tools

Lean, Inception, MVP, Figma, Kick-off, Product Vision, Is-is not does - does not do, Persona, Brainstorming features, User Journeys and MVP canvas.

Methods used

Lean inception

Participants

Designers: Tiago Diniz and Alison Almeida.

Developers: Robson Miranda, Adelson, Oliveira and Lucas.
‍
Stakeholders: Lucas Cardeal, Rodrigo, Alvaro and Eric.

Main goal

Bolunes was an old project that was on hold. Our goal was to decide where to start, what the MVP would be, to assemble the first solution that will be developed and placed in the hands of users.

The first thing I did was prepare a room for the remote workshop, then I made the appointment and defined who the participants were.

Pré - Inception

What I did before starting inception?

With a clear vision of the product, you can determine how your "pieces" of the business will fit together.

Bolunes is for Lunes customers who enjoy sports. They bet LUNES with friends for fun or to earn extra money.

Bolunes makes it possible to place sports betting with an innovative and unique experience. Unlike most betting platforms on the market, which are confusing and complex.

Our product allows customers to place bets using a LUNES wallet. As a way of betting totally innovative and different from the market.

Lean inception

Product Vision

Deciding what NOT to do is AS IMPORTANT as deciding what to do.Deciding what NOT to do is AS IMPORTANT as deciding what to do.

Divide a team into two groups and ask each group to fill in only the selected gaps in their authority model.

Is - is not does - does not do

If you have to break the product down into three business goals, what would they be?

I asked each person on the team to individually write three answers to the above question.

Product goals

An MVP needs to be: Pleasant, Usable, Reliable, Functional, Necessary and Segmented.

- Building an MVP isn't about cutting resources, it's about finding the minimum product you must build for the minimum audience you've set.

- Limiting the types of users you want to help goes a long way in reducing the needs you have to meet.

- What your audience expects from your product will define how much scope you will have to take on. Find those expectations and you can figure out what to build on.

Personas and User Journey

Anyone who thinks that an MVP is a product with a single functionality is wrong.

It is crucial to recognize the difference between what users want and what they expect. “Expectation” is how people believe something should work, while “want” is the desire for improvements in the current state of affairs. Falling short of desires can be bad, but not meeting expectations can be a disaster.

Functionality Brainstorming

Before starting to play features in the backlog it is important to prioritize, estimate and plan.

Here we choose the main features that meet the users' expectations. Then we define the levels of Effort, Business Value and UX Value.

Technical, Business and UX Review

The Feature Sequencer helps organize and visualize features and the incremental validation sequence of the product.

Sequencer

Canvas MVP helps the team to align and define the MVP strategy, the simplest version of the product that can be made available to the business (minimum product) and that can be effectively used and validated by the end user (viable product).

Canvas MVP

The main impact of applying the Lean Inception technique here at Lunes was the reduction of time to create digital products, something fundamental for companies in the technology segment that need to have quick responses to remain competitive in the market.

Prototype

Impact

Learnings

“The Inception is not a flower path.” — Tiago Diniz.

Perhaps companies that already work in an agile ecosystem find it easier to start introducing Lean Inception as a practice, as they understand the importance of achieving lean, flexible, incremental and adaptive planning.
‍
Here, it was not an easy task! And by the end of the workshop I was literally exhausted.

Getting participants to adapt to a new method is not easy.
What helped me was to try to show that the lack of planning could cause difficulties and even the failure of the project, resulting in a waste of time, effort, money, which could affect the quality.

‍
“Planning determines the success or failure of a project!” — Luana Monteiro.