Rafael Bisol

But even my closest friends calls me Bisol because it's my surname, haha. Anyway, this blog will talk about the solutions that I worked in and some techniques included in the product management role. I'll talk about one theme per post, like we're supposed to do in a project: divide everything that is possible to find the smallest chunk of work and turn that into a task.

Let's have a great time.

Cya,

This could be a song title: "Business' features"...

A long time ago I worked on an internal product that managed the entire customer journey: from when he was only a lead until the contract with him ended.

Wireframe of the internal product. Every customer of the company was listed in a specific screen of the product.

At that time we didn't have anything that identified the way the customer behaved with the company's products. This bothered me a lot because we didn't know how the clients were stimulated by the solution, so it could impact the Net Promoter Score (NPS) of other B2C products in our company. Our sales, support and marketing team used the information in that internal solution about the customers to make calls, do meetings, etc. So, in order to the company employees understand the customer's feelings and particularities about the product he hired, I thought about a tag system:

In my mind, that's how the tags worked. "Excited" means the customer was very excited about his product and "Sender" means he sends a lot of e-mails.

In order to validate my idea, I talked to the support and sales teams' coordinators and they said that this was a great idea. The first big thing we were suposed to do was a screen to manage the tags:

This is a CRUD (Create, Read, Update and Delete) for the tag system, listing each one that we had on the product and with the option of creating a new tag.

In order to specify the screen that enabled the tag management, I had to create a story for it. The story was composed by the following:

User story;

Acceptance criteria;

Risks;

Tests.

If the user wanted to create a new tag, the internal product should have the possibility of tag creation. This is a similar task to the issue I created for that:

I'm using Scrum in this example, but we actually used Kanban. This issue was created in Jira Software.

The feature was then worked on, reviewed by the developers and me and finally documented because this increment needed it. According to the Agile Manifesto we must have working software over comprehensive documentation.

The final result was, after managing the tags, a screen where we could attach the customer to a tag, given that we had the permission to do it.

The customer with the tags besides his name.

This is the case for today folks. I really liked this Tumblr stuff and I hope to do more in the future.

Cya,