Prepare information
Reuse documents, records and integrations. Ask users to resolve gaps.
HICX · Enterprise SaaS · UX & product strategy
Helping enterprise software
carry more of the work.
A product-experience strategy for supplier management: less manual effort, clearer decisions, and adaptive workflows that keep people in control.
TL;DR
- Role
- Senior UX / Product Designer · strategy & experience direction
- Team
- HICX · UX strategy
- Timeline
- 12-month proposed product direction
- Result
- Strategy framework and three interactive workflow concepts.
The central idea
Start with what people need to achieve.
Prepare the information. Make the next step clear. Bring decisions into focus.
Illustrative future experience
CONCEPT · ADAPTIVE COMPLETION
3 things left to complete your registration
Known information is prepared. You review what matters.
1
Confirm your company addressExtracted from your uploaded document · Unreviewed
2
Upload an insurance certificateRequired for approved-supplier status
3
Review your tax informationConfirm or correct the prepared details
01 / CONTEXT
Let the platform carry more of the work.
Supplier workflows asked people to enter information, coordinate handovers and work out the next step. I framed a platform-wide direction around three priorities: prepare known information, guide action and explain what the system has done.
02 / STRATEGIC CHOICES
Prepare. Guide. Explain.
Guide the next action
Make blockers, ownership and reasons visible in the workflow.
Explain the system’s work
Show sources, transformations and review status at the point of decision.
Prioritise workflows where these changes remove repeated effort. Keep approval, correction and recovery within the user’s control.
Explore the 12 candidate goals
03 / FUTURE EXPERIENCEIntent becomes a starting point
Intent becomes a starting point
for completing work.
Three concept interactions show how a goal can shape relevant views, suggested actions and outstanding tasks.
Interactive concepts · Fictional data · No real actions are sent.
04 / TRUST & CONTROL
Make reliability understandable.
“AI-generated” is not enough. I separated source, transformation and review status so users can decide what to check and what still needs approval.
Illustrative payment term
Checked against sourceNet 60
Source
Contract document
Page 12
Transformation
Extracted with AI
Not subsequently edited
Review
Checked by a reviewer
Approval still required
1. Prepared — Value extracted from the contract.
2. Checked — Reviewer compared the value with the source.
3. Awaiting approval — An authorised role must approve its use.
Illustrative history. Extraction, checking, and approval are distinct events.
Keep permissions, approval scope and recovery explicit before a consequential action.
05 / PROPOSED ROLLOUTQ1 Q2 Q3 Q4
Prove one workflow, then expand.
Establish
Observe work and baseline effort, delays and data foundations.
Pilot
Test one workflow with preparation, guidance and source visibility.
Extend
Apply successful patterns to adjacent workflows.
Review
Compare effort, task completion and recovery against baselines.
Proposed sequence from approval. Research and feasibility guide investment decisions.
06 / KEY TAKEAWAY
Automate effort. Preserve judgement.
The strategy defines what the system should prepare, what people should decide and how the interface makes that boundary clear.