Wave Accountability makes ownership visible. Give responsibilities a named owner, explain what success means, and connect that ownership to goals, scorecards, and Smart KPIs. Use the board to review who owns what, the chart to understand reporting relationships, and the Clarity Map to bring a person's role and outcomes together.
A growing team can have a busy task list and still struggle with responsibility. Who owns customer activation after the launch? Who decides whether a release is ready? What result should a role consistently deliver? Wave Accountability gives those questions a practical home inside Wave.
This guide covers the current Wave Accountability features, with a populated product showcase and an example you can adapt to your own team.
Watch the Wave Accountability product demo
The 48-second showcase follows Northstar Studio, a fictional six-person company preparing a customer portal launch. The workspace contains 18 responsibilities, three overlapping teams, seven goals, seven scorecard measures, and four Smart KPIs. The sample includes a reporting structure and a complete role definition for every person.
The showcase uses Wave’s actual interface components with fictional sample data. The people, responsibilities, targets, and results illustrate how a team can use the tool.
What is Wave Accountability?
Wave Accountability is the ownership workspace in Wave. It sits in Company navigation and offers three views: Board, Chart, and Clarity Map. Together, they connect responsibility, organizational structure, and the outcomes expected from each role.
A responsibility describes an area someone owns over time. A task describes an action to complete. For example, Riley owns Customer Activation. Preparing a welcome checklist or reviewing a specific customer's setup can become work in Wave Projects, while Accountability keeps the ongoing ownership clear.
In the demo, Riley's responsibility links to two goals, two scorecard measures, and two KPIs. The team can see an on-track activation result alongside an at-risk handoff measure. That creates a useful review conversation: what needs attention, who owns the response, and what evidence will show improvement?
Explore the guide: Board and discovery · Create and connect responsibilities · Maintain ownership · Reporting chart · Clarity Map · Getting started · FAQs
See who owns what
1. A shared accountability board
Board view organizes responsibilities by person. It provides a common place to review ownership across the organization without assembling a separate document for every discussion.
The sample board includes product direction, release readiness, design, customer activation, marketing, and engineering. A teammate can scan the board to find the owner of a recurring area of work before opening its details.
2. Member columns and responsibility counts
Each member has a column headed by their name and image or initials. A count shows how many responsibilities are in that column, and a creation control starts a responsibility for that member.
The count is a useful inventory signal. In the demo, each person owns three responsibilities. The number alone does not describe the effort or complexity involved; the definitions explain the scope.
3. Responsibility cards with context
Cards show a responsibility's name, descriptive content, and linked-item counts. This gives readers enough context to distinguish similar areas without opening every record.
For example, Customer Activation and Customer Handoffs both sit with Riley, but their definitions answer different questions. Activation concerns reaching first value; handoffs concern keeping ownership and next steps clear across teams.
4. Search responsibilities by name or identifier
The search control narrows responsibilities by name, record ID, or slug. Search for “Customer” when reviewing customer-facing ownership, or use a specific reference when following up on a known responsibility.
Search narrows the responsibility records, while member and team filters control the people in view. The current search does not treat the whole description as a full-text knowledge base.
5. Member and team filters
The Filter menu includes Member and Team. Member focuses the board on selected people. Team narrows it to members of the relevant group, with supported conditions for including or excluding matches.
The demo's Customer Launch view brings Maya, Riley, and Casey together. They contribute design, customer success, and marketing to the same launch. Filter preferences help retain a useful view; clear the relevant filters when you want to review the wider organization.
Create responsibilities and connect outcomes
6. Create a responsibility from the board
The main Responsibility action and the creation controls on member columns open the responsibility creation flow. Starting from a member column supplies that person's context. The form supports a title, description, assignee, and linked items.
A Create More option supports entering several responsibilities in sequence. When defining a role for the first time, start with a small set of distinct ownership areas, then read them together to check for gaps or overlap.
7. A clear title and rich description
The responsibility detail view provides an editable title and a rich-text description using Wave's canvas. Longer descriptions can be expanded or collapsed so the drawer remains readable.
Use the title to name the area of ownership and the description to explain its boundary, expected result, and review routine. Riley's Customer Activation definition covers the first seven days, a 90% activation target, and a weekly review of recurring friction.
8. A named assignee
The Properties section identifies the responsible member. A responsibility is assigned to one member, creating a clear point of ownership even when several people contribute to the work.
That owner can coordinate with teammates without making the responsibility ambiguous. Riley owns activation, Maya improves the customer journey, and Jordan owns release readiness. Those are connected responsibilities with distinct owners.
9. A grouped linked-item selector
Linked Items lets you connect multiple goals, scorecards, and KPIs to a responsibility. The selector groups the available records by type and includes search, making a longer list easier to navigate.
Available choices are scoped to the selected member and enabled tools. In the demo, Customer Activation has six links: two goals, two scorecards, and two KPIs. The responsibility stays readable while keeping its supporting outcomes close.
10. Link goals to ongoing ownership
Goal links connect a continuing responsibility to a defined result. A goal such as “Activate 90% of pilot customers in seven days” gives Riley a specific outcome within the broader Customer Activation responsibility.
The goal remains a separate record with its own status. Linking it makes the relationship explicit and adds to the goal count shown with the responsibility.
11. Link scorecard measures
Scorecard links connect ownership to recurring measures. The sample activation responsibility links to Pilot activation rate and Customer handoffs completed.
The first measure asks whether customers are reaching value. The second checks a supporting operating behavior. Together, they make the review more useful than a general statement that onboarding is “going well.”
12. Link Smart KPIs
Smart KPI links bring relevant KPI records into the same ownership context. The demo associates Total Active Users and Total Closed Conversations with Riley's responsibility.
These are prepared sample records and values. In a real workspace, KPI availability and freshness depend on the configured KPI and its data source. Accountability connects the records; the underlying KPI workflow manages their data.
Keep ownership useful as work changes
13. Reorder responsibilities within a column
The board supports dragging a responsibility to a different position within its owner's column. This lets a team arrange responsibilities in a useful reading order.
Put the role's most central ownership areas near the top. The order is a presentation and organization choice, not a separate priority score or a measure of performance.
14. Reassign a responsibility between people
Moving a card to another member's column changes its owner. Ownership can also be changed through the assignee field in the detail view.
When ownership changes, the existing linked items are cleared so they can be selected for the new member. Review the definition and reconnect the appropriate goals, scorecards, and KPIs as part of the handoff. Reassignment becomes more useful when the new owner understands the outcome and the supporting measures.
15. Work in a detail drawer
Opening a card reveals Responsibility Details while keeping the board context behind it. The drawer contains the title, description, attachments, Properties, Activity, and Comments.
Properties can be expanded or collapsed, and longer descriptions have their own expansion control. This gives a reviewer room to focus on the definition, the ownership fields, or the conversation as needed.
16. Attach supporting media and files
The responsibility drawer includes an attachment area with a Media & Files control. Its attachment flow also supports dropping files into the drawer.
A useful attachment might be an ownership brief, a process reference, or an example of an expected deliverable. Keep the description understandable on its own, then use supporting material to add detail. The showcase displays the attachment controls without uploading a file.
17. Review recorded activity
The Activity tab shows recorded events associated with the responsibility, including creation and supported updates. Entries identify the person, action, and timing.
The sample Customer Activation timeline includes its creation and a later update. This gives a teammate context for how the record has changed without reconstructing the conversation from memory.
18. Discuss responsibilities in context
The Comments tab keeps discussion attached to the responsibility. The shared comment flow supports comments, replies, and reactions, with management controls available according to the current user's access.
Use it to clarify a boundary, record a handoff question, or discuss an expected outcome. For a separate team conversation, move to the relevant Wave Chat workflow and reference the responsibility.
19. Copy references and move between records
Responsibility actions include Copy URL and Copy ID. The drawer also shows the record reference and provides previous and next navigation with a position count.
These controls help a reviewer move through a group of responsibilities or point a teammate to an exact record. A copied URL references the workspace record; it does not grant new access.
20. Remove obsolete responsibilities
The responsibility action menu includes Delete, with a confirmation flow. This supports keeping the ownership map current when an area is retired or replaced.
Before removing a responsibility, decide whether the work has ended or simply needs a new owner. A role change often calls for reassignment and an updated definition rather than losing the ownership record.
Understand the reporting structure
21. An accountability chart built from reporting relationships
Chart view arranges members according to their reporting relationships. Each member card includes their name, role title, and responsibilities, with counts for linked goals, scorecards, and KPIs.
In the sample company, Jordan, Riley, and Casey report to Alex. Maya and Sam report to Jordan. The chart brings those relationships and the actual areas of ownership into one view. Longer responsibility lists use a “more” summary to keep cards manageable.

22. Pan, zoom, and fit the chart
The chart provides zoom-in, zoom-out, and fit-view controls, with support for panning and moving nodes within the view. This helps navigate a larger organization or focus on a particular branch.
Use the overview to understand the structure, then zoom into a person or reporting line. Moving a node changes the visual arrangement in the chart; reporting relationships come from the member data and are maintained through the relevant member-management settings.
Connect role clarity to results
23. A member-by-member Clarity Map
Clarity Map brings a selected member's role definition, responsibilities, goals, scorecards, and KPIs together. A member list provides direct selection, while previous and next controls support reviewing people in sequence.
The showcase opens Riley's map. It answers why the role exists, what success looks like, what Riley owns, and which results deserve attention. The selected member remains visible as you move through the cards.
24. Role Purpose
Role Purpose explains why the role exists and the enduring value it creates. It gives the responsibility list a common direction.
Riley's sample purpose is to help every new customer reach their first useful outcome. That sentence helps the team decide which work belongs with customer success and which work needs another owner.
25. Success Outcomes
Success Outcomes describes the results the role should consistently deliver. The editing guidance encourages outcomes rather than a list of activities.
For the launch example, activating 90% of pilot customers within seven days is a concrete outcome. The associated goal and scorecard provide a way to review progress against it.
26. Core Obsessions
Core Obsessions identifies the things a person should keep returning to in the role. The form encourages a focused set of priorities that describe how the role operates.
Riley's examples are onboarding quality, customer feedback, response time, and handoff clarity. They guide attention when several requests compete for time.
27. Standards of Success
Standards of Success explains the expected quality and behaviors of strong execution. It makes the operating expectations more specific than a role title.
In the demo, Riley is expected to document next steps, close loops, and surface customer risks early. Those are practical standards a teammate can use when preparing or reviewing a handoff.
28. Company Impact
Company Impact connects the role's success to the wider business. It helps a person understand why their responsibilities matter beyond their own work queue.
Riley's role improves retention by making the first customer experience dependable. That connection gives the team a reason to care about activation and handoff measures together.

29. Edit the role definition in place
Members with the required administrative access can use Edit Clarity Map from the Role Clarity card's action menu. The drawer contains all five fields with prompts that explain what belongs in each one.
The current editing flow submits a field when focus leaves it. Keep definitions concise, specific, and aligned with the actual role. Review them after a meaningful change in responsibilities rather than treating the first version as permanent.
30. Review responsibilities within the Clarity Map
The Responsibilities card lists the selected person's ownership areas and the counts of linked goals, scorecards, and KPIs. This connects the role definition to concrete responsibilities without returning to the board.
Riley's Customer Activation row shows two links of each type. The other responsibilities remain visible alongside it, making it easier to discuss whether the role's ownership areas support its stated purpose.
31. See goals, scorecards, and KPI status together
Separate cards show the selected member's goals, scorecards, and KPIs with their relevant status indicators. Scorecard and KPI controls provide additional status context through tooltips.
These cards present member-associated records; they are not limited to the links on one responsibility. In the demo, activation is on track while a handoff goal and measure need attention. A review can begin with that difference and move into the underlying work.

32. Respect the workspace's enabled tools
Clarity Map availability follows the Accountability tool configuration. The Goals, Scorecards, and KPIs cards, along with the corresponding link choices and count chips, follow the enabled tools in the organization.
This keeps the view aligned with the workspace being used. If a card or link category is absent, check the organization's tool setup and your access before assuming that the member has no related work.
How to get started with Wave Accountability
- Define the ownership areas. List the recurring responsibilities your company needs someone to own.
- Choose one accountable member for each. Make collaboration explicit in the description while keeping ownership clear.
- Write the success boundary. Explain the expected result, important handoffs, and how the responsibility will be reviewed.
- Connect relevant outcomes. Add the owner's goals, scorecards, and KPIs that make the responsibility measurable.
- Review reporting relationships. Check Chart view against the organization's actual structure.
- Complete the Clarity Map. Define purpose, outcomes, core obsessions, standards, and company impact.
- Use it in a recurring review. Discuss unclear ownership, changes in scope, and results that need attention.
- Maintain it after role changes. Reassign responsibilities where needed and review their linked items for the new owner.
For the fictional launch, the review can start with Riley's at-risk handoff measure. The team can clarify the handoff standard, create follow-up work in Wave Projects, keep the process in Wave Knowledge, and use Wave Meetings for the next review. Wave Directory provides additional people and team context.
Feature availability and demonstration scope
Available views, controls, and linked records depend on your workspace’s enabled tools and your access. Accountability receives relevant responsibility updates to help keep its views in sync as ownership changes.
The video presents a prepared example. Its sample targets and results illustrate the workflow; they do not report customer or company performance. Connected KPI results depend on the configured data source and its latest update.
Wave Accountability FAQs
What is Wave Accountability used for?
Wave Accountability helps teams define who owns recurring responsibilities, understand reporting relationships, clarify roles, and connect ownership to goals, scorecards, and Smart KPIs.
How is a responsibility different from a task?
A responsibility is an ongoing area of ownership, such as Customer Activation. A task is a specific action, such as preparing an onboarding checklist. Accountability keeps the owner clear while task workflows manage execution.
What views are available?
Board view organizes responsibilities by member. Chart view shows reporting relationships and responsibilities. Clarity Map brings a person's role definition, responsibilities, goals, scorecards, and KPIs together when enabled.
Can I filter Accountability by team?
Yes. The filters include Member and Team. Search separately narrows responsibility records by name, ID, or slug.
Can responsibilities link to goals and metrics?
Yes. Linked Items supports goals, scorecard measures, and Smart KPIs associated with the selected member, subject to enabled tools. Multiple records can be linked to a responsibility.
What happens when I change a responsibility's owner?
The responsibility moves to the new member, and its existing linked items are cleared. Review the definition and select the appropriate goals, scorecards, and KPIs for the new owner.
What are the five Role Clarity fields?
Role Purpose, Success Outcomes, Core Obsessions, Standards of Success, and Company Impact. Together, they explain why a role exists, what it delivers, how it operates, and why it matters.
Who can edit the Clarity Map?
The in-place Edit Clarity Map action is available to members with the required administrative access. Other capabilities depend on the workspace configuration and the controls available to the current member.
Make ownership easier to understand
Start with a few clear responsibilities, give each one an owner, and connect the outcomes that matter. Use the board for the ownership conversation, the chart for reporting context, and the Clarity Map to explain what success means for each role.
Get started with Wave or talk with the Wave team about bringing accountability and everyday execution together.



