Create a Visual Responsibility Matrix from Approved Roles with Claude

A responsibility artifact is useful when you need to reveal unclear ownership across activities without assigning authority that was never approved. The result should make the underlying records easier to inspect and the next decision easier to explain. This guide develops a specific responsibility artifact with a source schema, operating rules, a fictional example, and observable review checks. It is intended for someone who already has the underlying material and needs a dependable way to organize it.

Product references checked: 7 October 2026. The examples and implementation specifications below are original editorial guidance. They illustrate expected behavior and have not been presented as a benchmark or as a completed tool tested inside another product.

Define the deliverable and its scope

The artifact visualizes approved responsibility; it does not reorganize the team or invent reporting lines.

Write the acceptance standard before asking Claude for a draft. A reviewer should be able to identify the activity id, inspect the role identifier, and understand the detail view without guessing what a blank field means. Decide which records belong in the deliverable, which are out of scope, and who can confirm the final interpretation. Keep those choices visible in the working specification rather than leaving the assistant to supply convenient defaults.

Prepare the source package

Gather activity IDs, approved role names, responsibility assignments, and accountability conventions. Assign source IDs and preserve original wording wherever a small difference could change the outcome. Record the collection date and the version of each source. If two files disagree, keep both references and mark the conflict. Do not replace a disputed value with whichever one produces the cleanest display.

Use a small representative subset for the first draft. Include one ordinary record, one incomplete record, and one record that challenges an important rule. For this task, use the following as the incomplete-record check: Add two competing accountable assignments and expose the conflict. Preserve the original package separately from the assistant's transformed output. A polished result is easier to audit when its IDs still lead back to the original supplied material.

Define the record schema

Treat activity id as a deliberate part of the data model. The stable work item to which responsibility assignments apply. Keep its representation consistent when you sort, filter, or revise the output. The role identifier field has a different job: An approved role, kept separate from the name of the person currently filling it. Combining these fields into one sentence can hide the distinction the reviewer needs to inspect.

Pay particular attention to assignment type and approval reference. The former means: The supplied responsible, accountable, consulted, or informed role for the activity. The latter means: The record authorizing this assignment and its applicable version. Store them separately and label both in the detail view or report. This makes disagreements visible at the exact point where they affect the result instead of burying them in a general note at the bottom.

Apply the task rules

Rule 1. Do not assume one accountable role unless that is the organization's approved convention.

Rule 2. Keep performing an activity separate from having authority to approve its outcome.

Rule 3. An empty intersection means no supplied assignment, not proof that the role has no involvement.

Rule 4. Flag conflicting assignments for review instead of silently choosing the most senior-sounding title.

Make these rules inspectable alongside the responsibility artifact. Ask Claude to describe how each rule affects a record and what should happen when the supplied data does not establish an answer. A rule written in prose still needs a defined output state. Use an explicit missing, disputed, or not-applicable label where appropriate, and reserve a valid zero or an empty result for cases where it has a defined meaning.

Work through a fictional example

A fictional release activity A-7 names the designer as responsible and the brand lead as accountable. A second source names the project manager as accountable for the same activity and version. The matrix should show the conflict and both approval references. It should not pick one because the title appears more senior. Another activity has no supplied accountable role and should be visibly incomplete. Clicking a cell should reveal the assignment evidence rather than only display a colored letter.

Use the example as a review fixture rather than as real operational data. Before generating the output, write down which fields should be populated and which should remain unresolved. Then compare the generated result with that expectation. If Claude supplies an unsupported value, correct the underlying instruction or calculation rule instead of merely editing the one visible record. Otherwise, the same error may return when the next record is processed.

Build the first version

Ask for the simplest interactive artifact that displays the schema and supports the specific review task. Start with the fictional example and an obvious detail panel. Keep the source data separate from display labels and interaction state. A selected row, a filter, or an open panel should change what the reviewer sees, not silently rewrite the underlying evidence. Add editing only to fields that the specification explicitly identifies as user inputs.

For the first interaction pass, prioritize ownership exception: A missing accountable role or conflicting assignment requiring owner review. Then add the detail view behavior: Explain the activity and the evidence behind each role assignment when selected. Use visible text labels for both. Test the core logic before spending time on animation or visual polish. Provide a keyboard path through the controls and preserve a readable empty state when the selected view has no records.

A reusable prompt

Create a responsibility artifact from the supplied source package. Goal: reveal unclear ownership across activities without assigning authority that was never approved. Use these fields: Activity ID: The stable work item to which responsibility assignments apply.; Role identifier: An approved role, kept separate from the name of the person currently filling it.; Assignment type: The supplied responsible, accountable, consulted, or informed role for the activity.; Approval reference: The record authorizing this assignment and its applicable version.; Ownership exception: A missing accountable role or conflicting assignment requiring owner review.; Detail view: Explain the activity and the evidence behind each role assignment when selected.. Preserve source IDs. Rules: Do not assume one accountable role unless that is the organization's approved convention. Keep performing an activity separate from having authority to approve its outcome. An empty intersection means no supplied assignment, not proof that the role has no involvement. Flag conflicting assignments for review instead of silently choosing the most senior-sounding title.. First explain the proposed data model and unresolved inputs. Then build the smallest usable version. Use only supplied facts; label the demonstration fictional. Do not invent approvals, thresholds, owners, or external integrations. Include an empty state and explain the expected result for these checks: Add two competing accountable assignments and expose the conflict. Replace a person's name while retaining the role identifier and check that assignments remain stable. Inspect the matrix using text labels rather than relying exclusively on color.

Review behavior and edge cases

Check 1. Add two competing accountable assignments and expose the conflict. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Check 2. Replace a person's name while retaining the role identifier and check that assignments remain stable. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Check 3. Inspect the matrix using text labels rather than relying exclusively on color. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Repeat the checks after adding another source record or changing the presentation. A working first example does not prove every record is handled correctly. Pay attention to retained selections, stale derived values, and unexplained changes in the number of displayed records. For responsibility artifact work, the reviewer must be able to tell whether a difference comes from new evidence, an edited rule, or merely a changed view.

Maintain the reviewed version

Keep a version label, source cutoff, and short change record with the finished responsibility artifact. Record who approved the rules and which demonstration cases were reviewed. When the source package changes, preserve record IDs and revisit the checks affected by the change. Do not treat yesterday's verified result as evidence that today's replacement input is complete.

Before handing the output to another person, review its audience and the material it contains. Use a sanitized demonstration for general feedback when the real source package is confidential. Explain whether changes are saved, whether the output is a preview, and which source remains authoritative. If persistence or sharing is required, verify that behavior in the actual account and intended environment instead of assuming it from a successful preview.

Frequently asked questions

Sources and related reading

Consult the current primary references for account-specific availability and controls: Current Claude artifact documentation, Claude sharing documentation. The schema, examples, prompts, and review checks here are editorial recommendations rather than documented built-in features.

For broader context, read the related Claude workflow guide.