Skip to main content

Implementation Phases

Current, next, later

This page turns the operationalization effort into execution phases with clearer timing logic. Use it to understand what should be tackled now, what depends on earlier decisions, and what should wait until foundational questions are resolved.

Phase model

  • current work resolves foundational decisions
  • next work turns decisions into supportable platform behavior
  • later work strengthens scale, reporting, and governance maturity

Current​

Identity and org decisions

The most important current work is clarifying the Okta path and authoritative Builder Relations org source.

  • confirm Okta SSO path
  • confirm claims and group usage expectations
  • confirm Builder Relations membership source of truth
  • define entitlement mapping principles
Platform assumptions

Current work should also define the assumptions needed before Kanopy and telemetry work can move from concept to implementation.

  • identify first Kanopy workloads
  • confirm environment and callback assumptions
  • confirm telemetry stack options and owners

Exit criteria for current phase​

  • named owners exist for identity, org truth, hosting, and telemetry
  • Okta path is explicit enough for implementation planning
  • Builder Relations source of truth is identified
  • first Kanopy scope is identified
  • telemetry ownership path is identified

Next​

Implementation and integration

Once foundational decisions are clear, the next phase should implement the operating layers that enable a supportable internal platform.

  • implement or plan Okta-backed workforce sign-in
  • implement org-aware entitlement mapping
  • prepare Kanopy deployment shape and runtime checks
  • define telemetry, dashboards, and audit events
Operational readiness

The next phase should also define the operational artifacts needed for a controlled pilot or limited rollout.

  • readiness checklist ownership
  • deployment verification path
  • access review cadence
  • leadership reporting baseline

Exit criteria for next phase​

  • identity and entitlement design is ready for implementation or pilot use
  • Kanopy hosting plan is specific and reviewable
  • telemetry baseline is defined and owned
  • readiness checklist can support a real pilot decision

Later​

Scale and maturity

Later work should improve quality and governance after the foundational operating model is working.

  • deeper leadership dashboards
  • stronger audit and access-review automation
  • more mature operational reporting and incident response
  • refined org-aware reporting and segmentation
Institutionalization

Later work should make the platform easier to sustain across teams and over time.

  • repeatable governance review cadence
  • stable ownership model
  • stronger internal onboarding and adoption support
  • clear long-term hosting and observability posture

Risk

Phase risk to avoid

Do not start the “next” phase as if the “current” phase were already resolved. Most downstream work depends on decisions about identity, org truth, hosting boundaries, and telemetry ownership.