Financial workspace
Bring balances, activity and available actions into one clear workspace.
No delivery metrics or client outcomes are asserted for this concept.
WORK
Product problems. Clear directions.
Explore illustrative product scenarios across web, mobile, desktop and operational software. Each concept shows how we turn a workflow problem into a product direction.
These are illustrative concepts, not completed client engagements or measured client results.
Work
- View concept
Everyday mobile service
Help users complete recurring tasks and understand their progress.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Workflow automation
Make approvals, handoffs and exceptions visible to the people responsible for them.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Creative production tool
Organize content, review feedback and local-file work inside a focused desktop experience.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Asset processing console
Configure work, follow processing stages and recover from failures.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Delivery flow workspace
Show where work waits and give blocked items enough context to act.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Knowledge library
Find shared guidance and understand which source to use.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Service configurator
Explore compatible options and review a configuration before submitting it.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Offline field notes
Capture observations and understand what is stored locally or ready to sync.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Mobile access pass
Present a workspace invitation and understand the scope of access it grants.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Data comparison desk
Compare local datasets and inspect differences before choosing what to keep.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Local environment manager
Inspect local development environments and choose which settings to apply.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Team capacity planner
Explore work allocation while keeping availability and competing commitments visible.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
System dependency map
Trace service relationships and inspect the context around a proposed system change.
View conceptNo delivery metrics or client outcomes are asserted for this concept.
Bring financial information into a clear workspace
The scenario
Users need to understand activity and status without guessing how different records relate to each other.
Proposed direction
The concept separates summary information, detailed activity and available actions. Every status has an explanation and an appropriate next step.
Questions to validate
- Can users locate an activity record and understand its state?
- Does the interface distinguish available information from pending updates?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Make a recurring activity easier to complete
The scenario
A daily service loses value when users have to navigate too much before reaching the action they came for.
Proposed direction
The concept gives the next activity priority, keeps progress understandable and makes notification preferences explicit.
Questions to validate
- Can a returning user complete the main action quickly?
- Can they understand and change how reminders work?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Make approvals and exceptions visible
The scenario
Manual handoffs make it difficult to tell which work is waiting, why it is blocked and who can resolve it.
Proposed direction
The concept provides a queue with explicit status, assigned ownership and a history of decisions, supported by configurable validation rules.
Questions to validate
- Can an operator identify a blocked item and its next action?
- Is the reason for a decision available to an authorized reviewer?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
A desktop workspace for creative production
The scenario
Creative teams need specialist tools that fit their review and iteration process.
Proposed direction
The concept combines content organization, review notes and preview behavior in a focused desktop application with clear local-file handling.
Questions to validate
- Can a creator find the current version and collect feedback?
- Does the tool recover clearly after an interrupted save?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Make a complex processing pipeline understandable
The scenario
Users need to configure work, follow progress and recover from failures without understanding every internal implementation detail.
Proposed direction
The concept makes input requirements, processing stages and failure causes visible in a unified workspace.
Questions to validate
- Can a user explain why a job failed and safely retry it?
- Can they distinguish a queued job from a stalled one?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Understand where delivery work waits
The scenario
A busy team may have little visibility into blocked work and long review queues.
Proposed direction
The concept makes work stages and waiting time visible while preserving context about scope, dependencies and rework.
Questions to validate
- Which stage accumulates waiting work?
- Does a process change improve flow without moving problems elsewhere?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Give shared knowledge a clear place to live
The scenario
Teams collect guidance across disconnected documents, making it difficult to find the relevant explanation and understand its scope.
Proposed direction
The concept combines topic browsing, focused search and a reading pane that keeps source context beside the guidance.
Questions to validate
- Can a reader find guidance using the language of their task?
- Can they tell which source applies to their situation?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Make product choices understandable before submission
The scenario
Users configuring a software service need to understand how their choices fit together before they send a request.
Proposed direction
The concept pairs selectable modules with a live configuration outline, explaining dependencies and preserving choices while users explore alternatives.
Questions to validate
- Can a user explain why an option requires another module?
- Can they revise a choice without losing the rest of the configuration?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Keep captured notes understandable across connection changes
The scenario
People recording observations on the move may lose connectivity or leave a note unfinished when interrupted.
Proposed direction
The concept provides a focused capture canvas, a local draft state and an explicit comparison when a shared note conflicts with a local edit.
Questions to validate
- Can a user tell whether a note is stored locally or shared?
- Can they resolve a conflicting edit without discarding an observation?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Make an invitation and its permissions easy to inspect
The scenario
People joining a shared software workspace need to check the destination and permissions before accepting an invitation on mobile.
Proposed direction
The concept places the invitation beside a readable access pass, showing the workspace, role and controls for leaving the shared space.
Questions to validate
- Can a recipient identify the workspace and role before joining?
- Can they find how to leave the workspace when access is no longer needed?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Give local data differences a readable structure
The scenario
People comparing local data files need to understand changed fields without losing the relationship between records.
Proposed direction
The concept aligns records in a split comparison, highlights field differences and provides a separate preview of the chosen values before export.
Questions to validate
- Can a user distinguish a missing value from a changed value?
- Can they inspect the chosen values before writing an export?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Keep local environment choices explicit
The scenario
Developers working across software projects need to understand which local settings belong to each environment before switching context.
Proposed direction
The concept combines an environment map with grouped settings and an explicit change preview, keeping project-specific configuration separate from shared defaults.
Questions to validate
- Can a developer identify which settings are shared across environments?
- Can they review the effect of a switch before applying it?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Make allocation choices visible before committing
The scenario
Teams planning shared work need to see how proposed assignments overlap with existing commitments and available capacity.
Proposed direction
The concept uses an allocation matrix and an unassigned work tray, allowing planners to compare draft arrangements before sharing a plan.
Questions to validate
- Can a planner identify overlapping commitments for a team?
- Can they distinguish a draft assignment from an agreed commitment?
Relevant services
No delivery metrics or client outcomes are asserted for this concept.
Keep system dependencies close to change decisions
The scenario
People maintaining connected software need to understand which services depend on one another before planning a change.
Proposed direction
The concept pairs a navigable service graph with relationship details and a change-scope overlay, keeping assumptions visible for review.
Questions to validate
- Can an operator trace the dependants of a selected service?
- Can they distinguish a confirmed relationship from one that needs review?
No delivery metrics or client outcomes are asserted for this concept.
Have a similar challenge?
Bring us the workflow, product idea or system you want to improve.
Discuss your project