Workflow Automation (WIP)

Research & Discovery

I started with understanding the entire workflow, and documented three separate journeys:

01 Existing workflow

How the original briefing process worked before the system migration.

02 Current workflow

How the new SharePoint/Nintex process behaved after migration.

This helped identify:

• duplicated actions

• unnecessary complexity

• broken interactions

• inconsistent system behaviour

03 Future Workflow

A simplified end-to-end experience representing how the process should ideally work for both requesters and the Design Team.

Journey Mapping and Hi-fi Design

I translated a complex workflow into a clear visual representation showing:

• user actions

• system responses

• decision points

• pain points

• opportunities

I also created a high-fidelity design of the future briefing form in Figma. It served as a communication tool that allowed developers and stakeholders to visualise exactly how the future workflow should function.

Prioritising by user impact

Rather than requesting every improvement simultaneously, features were grouped according to urgency and business impact.

Priority 1

Critical system failures

• Email notifications not being sent after form submission

Priority 2

Workflow improvements

• Simplifying the form

• Removing duplicated fields

• Improving information hierarchy

Priority 3

Future enhancements

Additional usability improvements identified during journey mapping.