Nicky's been a maker since his grandma bought him his first *real* toolbox when he was 4. His aunt taught him JavaScript when he was 12 and almost 20 years later, he still can't stop programming.
Of course! So first off it's a bit arbitrary but the idea was to have a simple framework that can be re-used time & time again and measure improvements.
So we consider that the user switches context when most of the page changes. A simple example is being on the login page and then being redirected to your dashboard. That's considered a context-switch. It might make sense but for the user they still went from one view to a completely different view. Unfortunately you kinda need to have that if you want secured workspaces.
Another example that can explain how we removed some context-switching is project creation. The process used to be the following starting from your dashboard:
(1) Click create project button
(2*) Be redirected to a project form
(3) Fill in the form
(4) Click create
(5*) Be redirected to the project
I put a star next to what was considered a context-switch. We changed that workflow to be:
(1) Click create project button
(2*) Be redirected to the new project with Untitled project
(3) Edit the name of the project inline
By removing the form there are less "screens" to go through and the user has less interfaces to learn. So the more we can let the user do actions in context the better.
Let me know if that makes sense.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Fascinating post and concepts! Really valuable.
One thing that wasn't mentioned was exactly how you define a "context-switch".
Maybe you could clarify that?
Of course! So first off it's a bit arbitrary but the idea was to have a simple framework that can be re-used time & time again and measure improvements.
So we consider that the user switches context when most of the page changes. A simple example is being on the
loginpage and then being redirected to your dashboard. That's considered a context-switch. It might make sense but for the user they still went from one view to a completely different view. Unfortunately you kinda need to have that if you want secured workspaces.Another example that can explain how we removed some context-switching is project creation. The process used to be the following starting from your dashboard:
(1) Click
create projectbutton(2*) Be redirected to a project form
(3) Fill in the form
(4) Click create
(5*) Be redirected to the project
I put a star next to what was considered a context-switch. We changed that workflow to be:
(1) Click
create projectbutton(2*) Be redirected to the new project with
Untitled project(3) Edit the name of the project inline
By removing the form there are less "screens" to go through and the user has less interfaces to learn. So the more we can let the user do actions in context the better.
Let me know if that makes sense.