How I used Skore to create a new feature in the Software
3 things to remember
- Set the scope first
My initial trigger (pre-requisite) : “software is installed”
Final business objective : “users know how to use the basics to create & share a Skore”
- Whatboxes describe actions
- Whyboxes describe why the action is done, why it is successful and when I can go to the next step
Transcript of the video
Hi, I’m Colin Claverie, one of the creator of Skore
Today I will show you how I have used Skore to create the tutorial that opens when you launch the software… what you see here in the background
I had this idea of a tutorial for a while, but I needed to translate it into requirements; I mean technical requirements; so I could understand the amount of work required to make it happen.
First, I always think it’s good idea to consider the context. In what context does the user operate and I don’t mean the things only in the computer, but the thing in the real life. I know my user got the software installed but they have no idea yet on how to use it.
And as we are at it, I will as well capture the final state so we have completely framed our story, the context.
Now that we have the context, let’s get started with how the tutorial works.
First I display a hint for the user so he or she knows what to do next. One of the main idea was to let the user do any action until the right one is done and then go to the next action
See how I can create new boxes very quickly, just hit the space bar (the shortcut I’m using the most)
It’s important to keep the motivation high 🙂 but in the background, the software prepares for the next step, and then we loop.
At this stage, I have the high level view of my user journey. I know what the user need to do (complete the actions one after the other). And I see what I need to do on the technical side
– I need to display hints
– I need to capture the actions of the user
– I need to prepare each step
You can see how I describe the user journey, using the WHAT box to describe what happens, I typically start with a verb to describe an action, and the WHY BOX describing why this step is necessary to the journey, I usually word them in a way that can be measured, so I know when I have the green light to go to the next step of the journey
So let’s go in more detail for the first action “display hint for action to do”
Here I will reuse the initial trigger of my WHATBOX and modify it slightly to fit my new story. I’m in the detail of “display hint” so I describe the kind of boxes I need for the user to understand what to do next
Be careful of using acronyms, they might not mean the same to everyone, here I’m using a Note to describe them
The last thing I need is technical change in the core software to capture the events of the user, so I have added this here too.
And Now I exit the detailed view; you can see the wings on the first box telling the box now has details.
I will show you one last way to attach more information to a box; let’s take the “Complete an action” where we understood that a “signal” has to be captured. I will use the paperclip to attach information. Can be a URL or TEXT.
So here we are with our Skore.
When I did it for the first time, it gave me a clear vision of what I needed to do. And what seemed to me like a fairly complex task at the beginning became something I could better understand.
Now let’s wire the business objective to my flow; and I have translated my business requirements (teaching the user) into technical requirements (what kind of hints, the signal story, preparing the next steps, etc.)
Of course, you decide which level of details you want to go for your Skore, but if you start by asking the right question, in the right context, the interesting topics will arise by themselves