Sample deliverable Orbit · Embedded Partner

Roadmap & Monthly Update

What you get from an Orbit engagement: a shared UX roadmap, progress you can measure every month, and guidelines that keep the product consistent.

Package: Orbit (Embedded Partner)

Product: Acme Approvals: purchase requests and approvals for mid-size companies

Rhythm: Weekly working session, monthly update

You receive: Roadmap, a spec for every feature, UX metrics, guidelines

This is a sample. Acme Approvals is a fictional product, and all numbers are illustrative. It continues the UX audit and spec samples.

The product

Acme Approvals is a purchase request and approval tool for mid-size companies. Employees request what they need, managers and finance approve, and a purchase order goes out to the supplier.

Acme Approvals, the My requests screen: three summary numbers and a list of purchase requests, most of them marked only as Pending. — Where we started in month one: most requests said “Pending” and nothing else.

Six-month roadmap

Built from the audit in month one and reviewed with product and engineering every month.

Month 1 Month 2 Month 3 Month 4 Month 5 Month 6 Audit UX audit and roadmap Spec & ship Status timeline, bulk approval, one term Requirements before the form Discovery Rule builder: research and spec Measure Monthly UX metrics review Guidelines Patterns and guidelines in the design system

UX metrics · month 4

The same four numbers every month, from product analytics and support data, so progress is visible to everyone.

status tickets per week

Was 41 −54%

18%

of requests sent back

Was 31% −13 pts

46%

of approvers use bulk approval

Was 12% +34 pts

2.6 days

median time to decision

Was 4.2 days −38%

Monthly update · month 4

One page for leadership: what shipped, what we learned and what comes next.

Shipped

Status timeline for all customers
Bulk approval with a selection summary
One term, "Request", across 42 screens

Learned

62% of overdue steps are decided within a day of a reminder
Approvers on mobile miss the selection summary
Admins want to copy rules between departments

Test "requirements before the form" with 5 requesters
Start rule builder research with 4 admins
Spec the selection summary for mobile

Guidelines · excerpt

Patterns are written down as they're solved, so new and old parts of the product feel like one product.

Status and progress

For everything that moves through steps: requests, approvals, purchase orders.

DoName who is responsible for the next step.

Don'tShow a status without an owner, like "Pending".

DoShow the time in step and the expected date.

Don'tShow raw timestamps only.

DoUse one term per object: "Request".

Don'tMix "Request", "Order" and "Ticket".

Term	Use for	Instead of
Request	Anything a user asks to buy or have approved	Order, Ticket, PR
Sent back	Returned for changes; can be resubmitted	Rejected
Delegate	The person covering for an approver who is away	Substitute, Proxy

How we work together

Weekly working session with product and engineering
Specs in your tools, reviewed with engineers before each sprint
Monthly usability tests with 3–5 of your customers
A monthly update like this one for leadership

Want this for your product?

Tell me about your product and your team, and we'll see whether an embedded setup fits.

Send inquiry