⌘K

Work Intelligence Console quickstart

Sign in to the Work Intelligence Console (WIC), find your way around your company’s work graph, and publish your first change to a Success Profile.

About the screenshots

Every screen on this page shows Acme Co., a sample company with 20,000 people, 15 departments and 53 Success Profiles. It’s the same company a trial account starts with, so you can follow along step by step.

Access

  1. Sign up for a trial.

    Use the sign-up link on the WIC login page. Your trial account comes seeded with the Acme Co. sample company, so you can start building workflows and asking questions right away. WIC labels it as a sample company.

  2. Upgrade when you’re ready.

    Email support@workerbee.ai to move to a paid account and start building your own company’s graph.

The company graph

You land on your company’s work graph: its departments, roles, people and the capabilities they hold. Each department has one curve to each capability area, and the curve is heavier where more of its roles’ requirements land. Departments and roles are sized by headcount. The totals underneath say when they were last counted.

The company graph: departments around the edge, capability areas in the middle, with totals for people, roles, relationships and capabilities underneath.
The company graph. Switch between Workerbee baseline and your company’s graph, between Graph and Table, and between 2D and 3D, or filter by departments, roles, open roles, people or capabilities.

Open Legend for what the colors, sizes and curves mean and how nice to have, core and non-negotiable capabilities are drawn. The canvas draws a sample of your people, in proportion to each department, so the graph stays readable.

The legend popover open under its button on the company graph.
The legend explains yellow (your company’s) versus gray (Workerbee baseline) and how many people the canvas is drawing.

Search covers your whole work graph, not only the people drawn. Search for a capability and each result shows its area and how many people hold it.

Search results for “kubernetes”, listing matching capabilities with their capability area and number of holders.
Searching for “kubernetes” finds every related capability and who holds it.

Departments, roles and people

Choose Departments in the sidebar, or click a department on the graph. Every department and role has its own Success Profile, and its page shows how well your workforce covers it: how many of its capabilities and non-negotiables someone here holds, and how many people across the company hold all of them. Each number links to the people behind it.

The Platform department page, showing headcount, roles and coverage of its Success Profile.
A department: its people, its roles, and coverage of its Success Profile.
The DevOps Engineer role page, showing headcount, open requisitions, non-negotiables and seniority split.
A role: headcount, open requisitions, non-negotiables, capability coverage and the Junior, Mid and Senior split.

A person’s page lists the capabilities on their profile and where they could move next: other roles’ Success Profiles, ranked by how many of their capabilities the person already holds, non-negotiables first. Where a non-negotiable is missing, the page names it. WIC counts capabilities; it doesn’t grade people.

A person's page listing other roles ranked by how many of their capabilities the person holds, with missing non-negotiables named.
Where a Senior DevOps Engineer could move next, with the non-negotiables they don’t hold yet.

Capabilities

Every capability and capability area has its own page, reached from the graph, from search or from a Success Profile. It shows who holds the capability, which Success Profiles name it, which roles expect it, and where it came from. If nobody holds a capability by that exact name, the page says so and lists related capabilities people do hold.

The Kubernetes capability page, showing holders, Success Profiles that name it, and related capabilities.
A capability page.

Success Profiles

A Success Profile is the standard every person is measured against. You have one for the company, one for each department, one for each role and one for each open requisition. Each inherits from the one above it, and the most specific profile decides a capability’s importance. Open Success Profiles in the sidebar to see them all, with what each inherits from and which version it’s on.

The list of Success Profiles, showing the company profile and department profiles with inheritance and version.
Every Success Profile, company and departments at the top level.

On a profile, yellow is what this profile defines and gray is inherited. The cards at the top show how many people are measured, how much of the profile someone here covers, how many profiles inherit from it, and its non-negotiables. A capability can be required at one seniority band and not another, so pick Junior, Mid or Senior to see each.

The DevOps Engineer role Success Profile, with coverage cards, seniority bands, a time slider and the profile's capabilities.
A role’s Success Profile, inheriting from its department and the company.

This profile over time is a slider across every recorded state of the profile. Step back to a publish to see who published it, when, and what changed; the graph redraws the profile as it stood then. The History tab lists the same changes with their reasons.

The time slider stopped on version 3, showing who published it, when, and the change it made.
The slider stopped on an earlier version.

Edit and publish a Success Profile

Changes wait in a pending bar until you review and publish them as a new version. Every publish is recorded with its author and reason, and it reaches every Success Profile that inherits from it and the agent’s answers.

  1. Open a Success Profile and choose Edit.

    Each capability this profile defines gets nice to have, core and non-negotiable controls and a remove button. An inherited non-negotiable is locked, and names the Success Profile that sets it.

    A Success Profile in edit mode, with importance controls on each capability and a short change, review, publish guide.
  2. Make your change.

    Change a capability’s importance and the row is marked pending and added to the bar at the bottom. Nothing is live yet. Inherited capabilities can be excluded here, or made less important with a reason, but an inherited non-negotiable can’t be excluded.

    A capability changed from core to nice to have, marked as pending in the bar at the bottom of the page.
  3. Add a capability if you need one.

    + Add a capability searches the whole catalogue and shows how many of your people hold each result.

    The capability picker searching for Terraform, showing how many people hold each matching capability.
  4. Review and publish.

    Review and publish shows exactly what the new version changes and how many Success Profiles inherit from this one. Add an optional reason (it’s kept in History) and publish. Publishing takes about 15 seconds. To reverse a change later, change it again and publish.

    The Review and publish dialog, listing the change, the profiles that inherit from this one, and an optional reason.

If someone else publishes the same profile before you do, your pending changes are kept so you can review them against their version.

Ask the agent

Every Success Profile, department, role and person has Ask about this. Pick a starter question or type your own. The agent answers from the same Success Profile the page shows, measured across your whole workforce.

The Ask about this profile box on a Success Profile, with starter questions.
Ask about a Success Profile from the profile itself.

The conversation lists each tool call the agent makes, then the answer: how many capabilities it checked and the closest people, ranked. Conversations are kept in the sidebar under Conversations, and each one can be downloaded.

An agent conversation ranking the people closest to the DevOps Engineer Success Profile, with the tool calls it made listed above the answer.
The agent ranks the people closest to a role’s Success Profile and shows the tool calls it made.

You can ask the same questions from Claude, ChatGPT or Gemini; see LLM Connectors.

WIC settings

Under Console in the sidebar:

  • Access shows who can open your company’s WIC. Everyone here works on the same work graph and Success Profiles; only the console owner can invite or remove people. Inviting colleagues needs a Team plan.
  • Connectors shows what an HRIS or ATS brings to your work graph. To connect one, talk to your Workerbee contact; see Integrations.
The Access page, listing the console owner and pending invitations.
Access.
The Connectors page, describing what an HRIS and an ATS add to the work graph.
Connectors.

Last updated