If you haven't already, check out the invitation to give us feedback on the User Experience beyond Tridion Sites 9 part 1 and part 2.

We're now implementing some of those designs, starting with Experience Manager. For a feel of what this may eventually include, here's a rough diagram of the different use cases or "jobs" a content editor can perform in Experience Manager.

This is based on lists of functionality that UX is gathering following a Jobs-to-be-Done approach (see a post how how Jobs-to-be-Done differ from Personas, by Page Laubheimer on the Nielsen Norman Group). For our scenarios, a job might be editing content, which in the current User Interface can be performed in a dialogue.

I'm then using the above diagram* as input into our stories in our next Program Increment. This is also a great way to reiterate a Basics First mantra that Tridion DX UI team member Raimond Kempees has been drilling into us since we formed the new team (and I passed on the donut).

In my next quick post, I'll share on ways to map the above stories to fit features, which is also guided by both technical and functional perspectives.

*Or one similar to it:
.