Intro

Delightree is a SAAS company which focus was to automate Standard Operation Procedures) SOP for franchises - they have pivoted since I left the company.

I joined the company when they had just got funding based on an MVP, and my task was to re-design the interface to make it a sellable product.

One of the hypothesis the product manager wanted to validate was that tasks would be created by store managers, which were part of the Deskless Workforce. Hence, they needed a way to create a task for their team.

Discovery

As part of the discovery process we had client interviews and input from the Customer Success team. Based on it, we created a list of requirements we needed to fulfill when creating a task:

1. A title for the task
2. A description for the task
3. Any attachments that were relevant for the assignee to complete the task
4. There were 2 modes
   1. Simple task
   2. Task with To-dos
5. Had to be scheduled for a specific day
   1. Could have a specific completion time
   2. Could be a one time task
   3. Could be a repetitive task
      1. Repetitive tasks had a set of different variations
6. Had to be assigned to different people
   1. Could be assigned to individuals
   2. Could be assigned to the whole store

Decisions

As it was a lot of information, we decided to break the creation into a step by step flow that reduced the cognitive noise and help them focus on the task at hand. It ended up being divided into a 4 section flow.

Details

The details section grouped everything that was related with the information the Assignee needed to know in order to be able to complete the task:

• Title
• Description
• Attachments

To dos

During the validation process we realised there were 2 main type of tasks: The ones that were a simple confirmation task (I’ve made it), while other required more actions. The actions that we identified during our research were:

• Checklist (sub-tasks)
• Take a picture
• Attach a file
• Write something
• Multiple choice
• Rating

Based on this, the second part of the flow was focused on helping the user choose what type of task to create.

Schedule

Also as part of our research and the data we had from the platform, we realised users created more repeating tasks than one time ones. That’s why we made this the default option. Also, we added the “Advanced settings” feature, which gave the users the flexibility to schedule their tasks with very complex settings while keeping it simple at first sight.

Assign

The last step of the flow was who to assign the task to. Users had the option to assign the task to a whole location where just 1 person from that location could complete it (Close the store, for example) and it’d be completed for everyone who belong to that store, or to a specific individual. We referenced Whatsapp and Facebook’s way of doing this in mobile, and mixed it with our specific needs.

Conclusion

In the end, we came up with a flow that took users smoothly through the whole task creation process, assuring them they were doing that they wanted to do and guiding them all the time. This had a high rate of acceptance and rose task creation metrics, which made it a successful project.