Defining/edit Journey (type/template)

[richardolsson]

Description

A user with sufficient privileges should be able to define a new journey template, or edit an existing one. The data belonging to a template is:

• Journey title – used to identify the template in the admin interface
• Journey label (singular) – used when displaying journeys of this type (e.g. "Clara Zetkin closed this case two days ago")
• Journey label (plural) – used when displaying collections of journeys of this type (e.g. "999 closed cases)
• Opening note text template – used as default value/template when user creates a new journey of this type, e.g. when a case worker opens a new case
• List of milestones, each with:
  • Title
  • Description (optional)

In the future, both the overarching template model, and the per-milestone model, may be extended with more configurable features.

Relevant Job Stories

• When our organization wants to start tracking a process that many of our members go through, we want to create a new "Journey" so that we can standardize the opening note and step-by-step milestones
• When I'm creating a new journey, I want to be able to pause and resume the process, so that I can have time to think about the configuration
• When I'm creating a new journey, I want to prevent users from using it until I've finished setting it up, so that we don't get misconfigured journeys in our database
• When a process in our organization changes, I want to make changes to the template without losing data, so that previous journeys still make sense

Prerequisites

None

Requirements

• [ ] There should be a page somewhere (TBD) to create new journey templates
• [ ] The process needs to allow an admin to configure the following:
  • [ ] Journey title (singular and plural)
  • [ ] Rich Text template for opening notes
  • [ ] List of milestones (each consisting of title and description)
• [ ] It should be possible to edit all of the above at a later time
• [ ] It should be possible to reorder milestones

Design specifications

See https://github.com/zetkin/app.zetkin.org/issues/574#issuecomment-1076599343

Open questions

• Where does this go? Settings section or Journeys section?

[richardolsson]

This was discussed in a recent UX meeting, and will need some design. Some notes from that meeting:

• Let's try to call the templates "Journeys", and the actual journeys by their template name (e.g. cases)
• User should be able to create a template quickly, and then iterate on it over some time
• We will likely want to solve this using a "draft page" rather than a modal
• Lets keep everything in a single tab, i.e. not milestones separately

[GemCopeland]

Hey @richardolsson @lowlandjuju,

I'm just going to put my design sketches in here, but let me know if you'd rather me start a Discussion about it instead so we don't clog up the issue.

Here's the overview of all Journeys:

I've put the templates in there for now, under the Manage tab:

People can edit/delete/duplicate Templates from there:

Or you can create a new one. It will open an "Untitled template" page where you can start editing things directly. I haven't added a Save primary action button because my assumption is that if we're using this pattern then it should be automatically saved. But also open to discussion on that one.

I've gone for a pretty simple page with lots of inline prompts to help people when they're filling it in.

You can click the title to change it:

Then you just add the summary:

And milestones:

What do you think?

[richardolsson]

Nice work @GemCopeland! I think it looks very good, but I do have a couple of suggestions that I'd like to hear your take on.

Terminology

First, I'm wondering if we should try to avoid the word "template", at least as the headline for this feature. I'd like to simply call the template a "Journey". Sometimes we use the word "journey" to refer to a specific instance of a journey, e.g. a case etc, but I think we should use the domain-specific name for those (i.e. "case"). Some sentences using this terminology:

My suggested terminology	"Template" terminology
Hey, can you set up a journey for casework?	Hey, can you set up a template for casework?
A member called me with some issues. I'm going to create a case for them	A member called me with some issues. I'm going to create a journey for them

Do you think that's going to be confusing? I'm just conscious that sometimes we present "feature" names very prominently instead of using terminology that explains the ROLE that the feature plays to the user.

Another example (for context) of this eagerness of ours to use feature names as UI is "Views", which is a great name for a feature, but I think a list of views should be headlined "People", not "Views", because that's why the user is there – to find people.

I'm honestly not sure what I think. 😊

Need for "Manage" page?

Secondly, I'm wondering if we really need the Manage tab? Maybe it's good to have it to keep things separate and what I'm about to suggest is not as good, but I think another option would to just move the functionality from the Manage tab to the Overview tab that is explained in #573.

• The menu option to "Edit" a journey/template could go into an ellipsis menu on each of the journeys
• The "new journey/template" option could go onto the big FAB, which would then look something liket his:
  • New case
  • New on-boarding
  • New enquiry
  • --Divider--
  • Configure a new Journey/template

[GemCopeland]

I really like both those suggestions!

100% agree about the naming – we can get so caught up on what a feature is on a technical level that it's easy to forget how someone with no context will see it and understand it.

Also like the idea of removing a tab and just having the create action in the FAB.

[GemCopeland]

New version starts here in Figma: https://www.figma.com/file/D4PrAup54f3vS4apqY3M7U/Journeys-MVP?node-id=1601%3A23692

Preview:

[richardolsson]

Cool @GemCopeland! I think this looks good. Only things I would change (but that can be fixed in development) is:

• Remove the "Duplicate" option, which is not something I think we've identified a need for – correct me if I'm wrong!
• Remove the "Delete" option. Not MVP, and we need to think about this some more