Skip to main content
UX Design Engineering
Settings

Settings

Theme
Text size
100%
Typeface

Chapter 10

Deciding what to share and supporting adoption

Evaluate reuse, domain differences, migration effort, and maintenance before proposing a shared pattern or adoption pilot.

Another product team sees the assignment flow and asks to reuse it for approving expense claims. Both tasks have eligibility, submission, and recovery. The screens appear similar, but approvals can have different permissions, audit requirements, and consequences.

The decision is what can safely be shared and whether the benefits justify adoption costs. Start with the teams’ actual needs before designing a universal workflow component.

Compare behavior before comparing appearance

Map the two workflows. Identify the actor, object, eligibility source, mutation, confirmation, and recovery path. Ask whether an uncertain outcome can be resolved with a record read or requires an operation-specific lookup. Check which facts need to remain visible for support or audit.

ConcernCase assignmentExpense approval question
AuthorizationCurrent assignment permissionDoes approval depend on amount, department, or delegated authority?
ConflictCase state changesCan another reviewer approve or reject concurrently?
Uncertain resultRead latest assignment in the simple caseIs a durable approval-operation record required?
RecoveryReview current case and choose next actionWhat actions are allowed after a recorded approval?

The expense questions are fictional prompts, not claims about a specific policy. A visual similarity is a starting point for investigation.

Choose the level of sharing

Several outcomes are reasonable. Teams might share a written recovery pattern and test scenarios while keeping domain implementation local. They might contribute an accessible feedback primitive to the component library. If the service guarantees align, they might share a small operation-state helper. A full workflow abstraction requires stronger evidence.

Separate stable interface behavior from domain rules. A shared status announcement component should not decide whether an expense is authorized. A common helper should document which service guarantees it assumes.

Use Building your own component system for library implementation techniques. Here the task is choosing the boundary and agreeing on what maintenance that boundary creates.

Account for the cost of adoption

Estimate integration effort with the adopting team. Include framework compatibility, existing customizations, accessibility review, testing, release scheduling, training, and ongoing support. A team may reasonably decline to migrate a stable workflow during a customer commitment.

Name who maintains the shared part, who maintains adapters, and who owns the product-specific behavior. Agree on supported versions and what happens when a new requirement conflicts with the original pattern. Unfunded maintenance is still a cost; it is merely absent from the initial estimate.

Staff practitioners often contribute most by making those commitments feasible. A reference implementation can clarify the solution, while a funded migration pilot tests whether another team can use it.

Start with a bounded pilot

Choose a team already changing a relevant workflow. Agree on the smallest shared contribution, a support contact, an evaluation point, and an exit path. Record the assistance provided so a successful pilot does not hide a large continuing dependency on the author.

Evaluate product quality and adoption separately. Can users complete the task accessibly? Can the adopting team integrate and maintain the pattern without recurring intervention? Measure actual use, integration effort, unsupported cases, support demand, and the cost of upgrades. Demo attendance and package downloads answer different questions.

When a second environment exposes a weak boundary, revise or narrow it. Do not convert every local variation into another option on a shared component until the combined API becomes harder to understand than separate implementations.

Include a local exception

In the worked case, the expense team may reuse the recovery guidance while retaining its approval service and domain-specific interface. That can be a successful outcome. Document the shared principle and the reason implementation stays local, then revisit the choice if future evidence changes it.

A mandate to standardize should be assessed against the same costs and quality expectations. Consistency has value when it supports people and teams; it still requires a workable migration and support plan.

Practice: propose an adoption decision

Compare your workflow with a second domain. Recommend a shared pattern, primitive, helper, or local solution. Define the behavioral contract and its assumptions. Estimate adoption and maintenance effort with the people affected, or label the estimates as unverified.

Write a pilot proposal with scope, owners, support capacity, evaluation criteria, and exit conditions. For an advanced exercise, ask another person to integrate the artifact using its documentation and record every intervention you provide.

Review your work

The recommendation should explain what is shared, what remains local, and who supports both. Your evidence should distinguish “another team can use it” from “the author can make it work for another team.”

The next chapter uses the difficulties you encountered to choose a deliberate learning task.

Found an error? Report it.