Guides, frameworks, and the thinking behind them.
Written by the architects who run the work. Every statistic carries its source.
Every piece.
Field notes
Why your Atlassian user count is wrong, and it's not headcount
When the licensed user count in Atlassian Guard does not match headcount, the gap is group structure, not people. The fix is a group model.
Why a phased Jira migration can be the riskier choice
When spaces share links, roll-ups, scripts and global apps, phasing a Jira migration splits one system in two. A rehearsed single cutover is safer.
Why capacity planning in Jira starts with cleanup
Cross-team roll-ups and capacity planning in Jira need shared teams, workflows and fields first. Clean up and tighten admin rights, then plan.
What happens to your ScriptRunner scripts when you move to Cloud
ScriptRunner scripts rarely move to Cloud as they are. Inventory them, read the code, then choose native Jira, Automation, Forge, a rewrite or retirement.
How SSO and user provisioning closed an Atlassian access gap
Local Atlassian passwords let former employees log in and hold licenses. Enforcing SSO through Okta and turning on provisioning closes that gap first.
Building a Forge worklog integration that holds up under load
A Forge worklog integration holds up at scale when it is designed around Jira roles, small API calls and mapped user IDs, with staging and alerts.
Where identity debt hides in a migration
The nine places inherited permissions surface in a Data Center to Cloud migration, from dormant accounts to agents that inherit whatever the humans had.
Assessing agent readiness before your first Rovo rollout
A ten-item checklist for a first Rovo rollout: identity, scope, ownership, attribution, change control, budget, and what happens when the agent is wrong.
Frameworks
The four-layer model for an accountable system of work
Identity, platform, governance, agents. A dependency model for diagnosing why a platform problem keeps coming back after it was fixed.
Okta and Atlassian Guard, mapped to one identity model
A decision-by-decision map of what belongs in Okta and what belongs in Atlassian Guard, plus where the boundary between them usually goes wrong.
What change control needs before agents touch it
Eight controls change management needs before an agent acts: definition, identity, ownership, scope, attribution, reversal, blast radius, and cadence.
Scaled agile and governance, without slowing delivery
Why approval-shaped governance slows delivery, and the four structural mechanisms that yield audit evidence and portfolio reporting from ordinary work.
Get an agent readiness assessment
Fixed scope. You get a findings report across identity, platform, and governance, an ownership gap analysis, and a sequenced plan for closing it.
By sending this you agree to our privacy policy.