Consulting & Pricing

A Workflow Change Impact Assessment: Map What Each Role Must Do Differently

The form is ready.

The requester still has an email draft. The reviewer cannot see the queue. The fulfillment coordinator has two places to check for work.

“Move requests into the new system” leaves those differences buried inside a project milestone. Write down what each role must do differently. Then identify the decisions, access, and instructions that action requires.

UCSF's change impact assessment guidance compares present and proposed work and identifies affected people and information needs. Prosci's change-impact framework brings an organizational initiative down to changes in individual jobs. Those are the source concepts. The worksheet below is a proposed method for one small workflow, with fictional evidence throughout.

Put One Workflow Inside the Boundary

Consider a fictional service team replacing shared-inbox intake with a request form and queue. Requesters submit work. Reviewers check completeness and assign accepted requests. Fulfillment coordinators complete assigned work and record the outcome.

The proposed change covers intake, review, assignment, and closure. It excludes billing, employment terms, and service-level commitments. The process owner has approved that scope. Detailed preparation decisions remain open.

Write the boundary above the assessment. Include the workflow owner, proposal version, affected roles, and review date. A reader should know which change the rows describe without opening another presentation.

Keep the transition decision separate from proof of readiness. Approval to introduce the form does not establish that each requester can open it. Approval also does not define what happens to requests already sitting in the inbox.

Connect the boundary to the consulting project plan. The project plan carries milestones and dependencies. The assessment supplies the task differences behind those milestones. Keep each record responsible for its own question.

Describe the Current Work Before the Future Work

Start with a normal request. Ask each role to describe its action, input, output, and next recipient. Use synthetic material when a demonstration would otherwise expose private records.

In the fictional current workflow, the requester emails the shared inbox with a subject line and attachment. The reviewer replies when required information is missing. An accepted request moves to a coordinator through a forwarded message. The coordinator replies when work is complete.

That description contains assumptions worth checking. Does forwarding establish assignment? Who watches for incomplete requests? Where does the requester find the final answer? Record each unknown until the affected role confirms it.

Describe the proposed path with equally concrete verbs. The requester submits required fields through a form. The reviewer marks completeness and selects an assignee in a queue. The coordinator records completion against the assigned request identifier.

Avoid replacing detail with “use the portal.” Someone still needs to decide which attachment belongs in which field. Someone needs to recognize a request that should remain pending. The application name does not answer those questions.

Copy This Role-by-Task Impact Matrix

Create one row per changed action. Split rows when their evidence, dependency, or owner differs. A role can have several rows.

Role and task Current action Future action System dependency Evidence to review Unresolved impact
[Role: observable task] [Action and output today] [Action and output proposed] [Access, input, or service required] [Observed sequence or approved rule] [Question, owner, and review point]
Requester: submit Email the shared inbox Submit form and retain request identifier Form access and confirmation view Synthetic submission and requester walkthrough Attachment rule needs process-owner decision
Reviewer: check Reply to missing information by email Mark incomplete and request correction in queue Review permission and missing-information status Sample incomplete request reviewed with reviewer Correction notification is unverified
Reviewer: assign Forward accepted email Select queue assignee Assignment permission and eligible assignee list Assignment recorded on a synthetic request Backup reviewer coverage is undecided
Fulfillment: complete Reply to forwarded message Record outcome against queue identifier Assigned-request access and closure field Coordinator walkthrough and proposed procedure Requester closure visibility is unverified

These entries describe a proposed workflow. They do not report a product's default behavior. Confirm the actual application's version, configuration, permissions, and notification settings before replacing them with operational claims.

Keep current evidence and future evidence distinct. A documented inbox procedure supports the current-action column. A queue demonstration supports a particular proposed action in the demonstrated configuration. Neither proves that every role has the required access.

The table is deliberately narrower than Prosci's full framework. It focuses on observable tasks and dependencies. It does not reproduce Prosci's template or assign employees attitudes, motives, or beliefs.

Walk Through the Requester's Changed Action

Use a fictional record called SR-014. It requests a revision to an internal service guide and includes one synthetic attachment. No customer, employee, or account information belongs in this example.

Under the proposed rule, the requester selects a request type, provides a description, and attaches supporting material. The form returns an identifier. The requester retains that identifier for later questions.

During the fictional walkthrough, the requester can open the form but cannot tell which request type fits the guide revision. Record the evidence precisely: the available labels do not resolve this sample. Do not record “requester resists the form.” No observation supports that judgment.

Assign the taxonomy question to the process owner. The owner must either clarify the existing label or approve a revised choice. The evidence needed is an accepted field definition applied to SR-014.

Separately, ask whether the requester can see a confirmation after submitting. That is a system question. A better explanation of request types will not repair a missing confirmation screen. Keep the access and procedure questions in different rows.

Once the proposed action is clear, identify the communication need: where requesters submit new work and which identifier they retain. That message can cite the approved rule. It should not describe an undecided field as final.

Follow the Reviewer and Fulfillment Handoff

Continue with SR-014. In the fictional review, the attachment is missing a required revision note. The reviewer needs a way to mark the request incomplete and identify the missing input.

The matrix now needs a decision about ownership while information is missing. Does the reviewer retain the request? Can a coordinator receive it? The process owner must answer before the procedure can describe the handoff.

For this example, the proposed rule keeps incomplete work with the reviewer. Assignment becomes available after the completeness check. That rule is invented for the worksheet. Confirm the corresponding rule in your own workflow.

After the missing revision note arrives, the reviewer confirms completeness. Then trace the accepted request into fulfillment. The reviewer chooses an eligible coordinator. The coordinator must distinguish assigned work from requests awaiting review. Record the required view and permission in the dependency column.

During the synthetic walkthrough, the coordinator can open SR-014 but cannot find the closure field. Record the missing field as an unresolved impact. The system owner must determine whether configuration, permissions, or an incorrect procedure caused the gap.

A business system dependency map can hold the deeper relationship between queue access, identity, and required services. Reference that map from the assessment. Avoid turning the role matrix into an inventory of every application.

Separate Access, Procedure, and Communication Needs

Give each finding a preparation type. This is a proposed sorting rule for assigning work, not a diagnostic standard.

Access asks whether the role can reach the required screen, record, or action. Procedure asks which action the role should take. Communication asks what confirmed change the role needs to hear and when.

SR-014 produces three different preparation tasks. The system owner investigates closure-field visibility. The process owner resolves the request-type definition. The transition coordinator prepares a notice explaining the submission location and identifier.

Do not merge them into “team needs training.” That sentence skips the decisions still missing. A lesson cannot establish an undecided rule or grant an absent permission.

Use the assessment to define the changed action before selecting a learning intervention. Stop this document at task differences and preparation needs. A separate training-needs analysis can investigate whether instruction is appropriate after the action and conditions are clear.

When an approved procedure changes, update the relevant standard operating procedure. Keep the assessment's reference tied to that version. Readers should be able to distinguish an approved instruction from a suggested correction.

Give Every Open Question a Review Owner

The matrix reveals differences. A small follow-up record makes the unanswered questions assignable.

Impact question Preparation owner Readiness evidence Review owner Status
Which type covers guide revisions? Process owner Approved definition applied to SR-014 Requester representative Open: definition missing
Does incomplete work remain with review? Process owner Accepted routing rule and revised procedure Reviewer representative Proposed rule awaiting review
Can fulfillment record closure? System owner Authorized coordinator sees and uses closure field on synthetic record Fulfillment representative Open: field absent in walkthrough
Where do existing inbox requests finish? Transition coordinator Accepted boundary rule and inventory of pending work Process owner Open: transition decision needed

The preparation owner produces the answer or remedy. The review owner checks whether the evidence resolves the stated question. Name people in a real assessment. Role labels are placeholders here because every participant is fictional.

Add a review date to each open item. When the answer is unknown, record the next investigation step. A date without a question and owner becomes another milestone nobody can evaluate.

Do not average these rows into a readiness percentage. Closure access and an unclear label have different consequences. For this worksheet, evaluate each required condition directly and record any condition the process owner accepts as unresolved.

Validate the Matrix With the Affected Roles

Bring the current and proposed actions back to the people who perform them. Ask whether the sequence matches their work. Ask what happens at an exception, handoff, absence, and return for missing information.

Preserve disagreements. A reviewer may describe assignment as complete when a message is forwarded. A coordinator may describe it as complete only after accepting the work. Record both descriptions and assign the boundary decision.

Keep the discussion anchored to tasks. Ask what a participant sees, receives, changes, and passes onward. Do not turn a missing step into a claim about competence or willingness.

Finish by labeling each row confirmed, proposed, or unresolved. Record who reviewed it and which evidence they examined. Confirmation applies to the stated action and conditions. It does not establish readiness for every possible request.

The assessment is ready to inform preparation when every changed task has a traceable difference and every unresolved impact has an owner. The process owner still decides whether to proceed.

Make the changed work visible.

Sources

Topic map: Records, access, and continuity

Articles in this cluster, then the 3 clusters that share the most topics with it.

This cluster: Records, access, and continuity

Neighbor: Business reporting and statistics

Neighbor: Spreadsheets, CSV files, and data handoffs

Neighbor: APIs, webhooks, and automation