Process & product improvements / Future-state concept

Intelligent Treasury Orchestration Platform

A concept for moving from transaction-first forms toward an experience organized around the user’s intent and the decisions needed to act safely.

Portfolio-safe derivative of product thinking. The map below is a fictional concept, not an implemented Truist flow. It omits internal systems, architecture, metrics, and proprietary rules.

Problem

Complex treasury tasks can scatter setup, policy feedback, approvals, and corrections across separate moments. Users may discover a blocker late or lose confidence in what changed after submission.

What I Designed

An intent-led journey with guided inputs, earlier risk feedback, a safer correction path, and a visible history of decisions. The design principles are clarity before commitment, progressive guidance, explicit control points, and traceable change.

Artifact

A reconstructed experience map and a sample change-handling pattern, expressed without source screens or implementation details.

Why It Matters

It gives product, design, engineering, risk, and operations a common way to discuss the whole journey, including exceptions, before choosing a solution.

Artifact / Future-state experience map

From intent to accountable outcome

01 / IntentState the goal“Move funds to a saved destination next week.” Begin with the purpose, not a product form.

02 / GuidanceShape the instructionAsk only for details needed at this step; show the next decision and available options.

03 / Early feedbackSurface constraintsIdentify missing information or policy questions while there is still a clear path to fix them.

04 / ControlReview & approveSummarize the instruction and make the handoff to any required approval explicit.

05 / VisibilityTrack the outcomeShow current status, decision history, and a safe next action if the instruction needs attention.

Example correction path

Moment	Experience response	Control preserved
A submitted instruction needs a material correction	Show the current and proposed details side by side, with the reason for the change.	The original decision remains visible.
The user confirms the revision	Reassess applicable checks and explain whether another review or approval is needed.	Do not silently carry forward a prior decision to changed details.
The revision is accepted	Display the new status and a readable sequence of who changed and reviewed what.	The history supports follow-up and audit review.

These are design principles and example interactions; exact eligibility and approval policies remain open for validation.