Skip to main content
ClrSlate
Request a demo

Solution · Organization change

Change the organization

A team split, merged or renamed as a job with an owner, not a slide and three months of confusion.

Request a demo

Split, then Marcus decides, then New chart.

Who decides · Marcus Oyelaran · Department head · teams split, merged or renamed

How it runs

A team is split, merged or renamed. Without ClrSlate that is a slide, an announcement and three months of people not knowing where to send a request. As a job, the seats move with their reporting lines, the requests are re-pointed, and the agents keep what they know.

A seat is a role a person and an agent hold together; the escalation matrix says who decides above each limit, seat by seat.

  1. Person decidesMon
    Marcus raises the split
  2. Agent carriesMon
    Prepared against the operating model
  3. Rules checkMon

    ORG-R02

    The shared runbook is not covered

  4. Person decidesTue
    Beatriz Alves agrees the runbook split
  5. Person decidesWed
    Marcus approves the split; DEC-3105
  6. Agent carriesWed
    Chart, seats, requests and runbook moved
  7. Rules checkNext week
    A vacant seat goes to the next one up
up the escalation matrix, by rule a person decides

Your team chat · #platform-ops

Enterprise Architecture agent Agent

The split is prepared. One part needs review: the runbook both teams depend on.

Waiting on Beatriz Alves

Split the runbook by platform; keep the shared pages under DevOps

AgreeAsk for changes
Drawn as your tool shows it; ClrSlate adds the line that names the owner.

Illustration · Corvane, a fictional company

Step by step

Who takes each step, in order.

For

Told end to end: Corvane splits its platform team. Corvane is a fictional company.

  1. 01Marcus Oyelaran, department headRaises the change: two teams, their lead seats, which seats move where, the cost centres.
  2. 02His agentPrepares it against the operating model and the procedure for splitting a team.
  3. 03Beatriz Alves, Enterprise ArchitectureReviews the one thing the procedure does not cover, the shared runbook (ORG-R02), and adds the rule to the procedure.
  4. 04Marcus OyelaranApproves the split and names the leads; a vacant lead seat is covered until filled (DEC-3105).
  5. 05Enterprise Architecture’s agentCarries it out: the org chart, the reporting lines, the requests re-pointed, the runbook split.
  6. 06The teams’ agentsKeep their identities and what each seat knew.
  7. 07The escalation matrixSends the vacant seat’s first request to the next filled seat up.

Where the decisions sit

Decision, who decides, up to where, and above that whom.

  • A new product team, with owner, sponsor and cost centreDecides: the department headUp to: the approved procedureAbove that: the executive
  • A new practice, or a platform team under oneDecides: the department head, after Enterprise Architecture reviewUp to: the operating model as publishedAbove that: the executive
  • Teams merged, split, renamed or archivedDecides: the department headUp to: the approved procedureAbove that: Enterprise Architecture, when the model itself changes

How much the agent decides, to start. The agent in the Enterprise Architecture seat prepares every change against the model and drafts the new chart; it decides nothing. The department head decides every time.

The record it leaves. One organization change, one Enterprise Architecture review with its proposal, decision record DEC-3105 with the seats and cost centres it named, the procedure’s new rule, and the org chart’s versions before and after.

How it plugs in

No new inbox, no new tool to learn.

  • 01

    An app in your tools

    Connects to your repositories, trackers and chat as an app

  • 02

    A check, not a meeting

    Holds a decision as a check the owner clears

  • 03

    Where people already work

    Asks the owner where they already work, and carries out what was decided

CO
Org chart

Organization change

Split the platform team in two

  • Kubernetes platform teamNamespaces, capacity, clustersDmitri Volkov
  • Cloud platform teamProjects and the landing zoneVacant · Dmitri covers
  • Runbook · DevOps practicePages both teams depend onShared standard
rulesORG-R02: the runbook split is reviewed by Enterprise Architecture
personMarcus Oyelaran approves the split
agentRequests re-pointed; agents keep their identity and memory
Corvane · DEC-3105
The change, with the seats it moves and the one review it needed.

The tools it runs through

We connect to the systems you run, and build the connection before the demo.

What it uses

Where it leads

Start with howyou run today.

Bring one piece of work that breaks at the handoffs: a pull request waiting on three reviewers, an initiative spread across twelve tools, a release nobody owns. We model the seats it crosses, give one of them an agent, and follow one decision to its record.

Request a demo