---
name: practice-management
description: Use when asked how to run a professional practice — either a discipline-based community of practice inside a larger organization (e.g. a UX practice, an engineering practice) or a client-facing professional practice (legal, medical, consulting) — covering practice standards, capability development, and utilization/workload management. Distinct from managing one project or program (see project-management, program-management).
---

# Practice Management

"Practice management" covers two related but distinct senses, both about
running an ongoing discipline rather than a bounded piece of work:

1. **A community of practice / discipline practice inside an
   organization** — e.g. "the UX practice," "the engineering practice" —
   the group of people sharing a discipline across many teams/projects,
   plus whoever leads and develops it.
2. **A client-facing professional practice** — a law firm, medical
   practice, consultancy, or agency — an actual business unit or
   organization delivering professional services to clients.

Both senses share a common structure: setting standards for how the
discipline is practiced, developing the people who practice it, and
managing how their time/capacity is allocated — this skill covers both,
noting where they diverge.

## Practice standards

A practice defines **how work in its discipline should be done** —
templates, review checklists, tooling choices, quality bars — distinct
from any single project's own standards, because the practice's standards
are meant to hold across every project/client the discipline touches. A
practice with no shared standards produces wildly inconsistent quality
depending on which individual happens to be staffed; a practice with rigid
standards and no room for context-specific judgment produces compliance
theater instead of genuinely better work. The right level sits between:
a small set of genuinely load-bearing standards, with clear rationale for
each, rather than an exhaustive checklist nobody actually reads.

## Community of practice (internal sense)

- A **community of practice (CoP)** is the group itself — practitioners
  meeting regularly (guilds, chapters, communities) to share knowledge
  across project/team boundaries, since day-to-day project work rarely
  creates space for that on its own.
- A **practice lead** (chapter lead, discipline lead) typically owns
  capability development (career paths, skills frameworks — see
  [[united-kingdom-government-digital-and-data-profession-capability-framework]]
  for one real, published example of a capability framework a practice
  might use) and practice standards, often *without* line-management
  authority over practitioners who report into project/product teams day
  to day — a structure that only works if the practice lead's authority
  over standards and the line manager's authority over people are both
  respected rather than in tension.

## Client-facing practice (professional-services sense)

- **Utilization** — the proportion of a practitioner's available time
  billed to client work, a core financial metric for a fee-earning
  practice; too low and the practice isn't covering its costs, too high
  (sustained) and there's no time for practice development, training, or
  non-billable capability building — either extreme is a warning sign, not
  just the first one.
- **Realization rate** — billed amount actually collected versus the
  practice's standard rates, distinct from utilization; a fully-utilized
  practitioner billing at heavily discounted rates still under-recovers.
- **Capacity planning** — matching practitioner availability and skill mix
  to expected client demand, ahead of time rather than reactively — the
  professional-services analog of [[portfolio-management]]'s
  capacity-based sequencing, applied to people instead of projects.

## Common pitfalls

- **A practice lead role with responsibility but no real authority** —
  expected to raise quality and standards across the practice while every
  actual staffing/priority decision is made by project/team managers
  elsewhere; without at least some real lever (input into staffing,
  standards sign-off, or budget), the role becomes advisory in name only.
- **Standards created once and never revisited** — a practice's tooling
  and best-known-methods should evolve as the discipline does; a
  standards doc untouched for years is usually being quietly ignored.
- **Sustained over-utilization treated as a success metric** — a
  consistently 100%+ utilized practice has no slack for training,
  standards work, or recruiting/onboarding capacity, which shows up later
  as burnout or a capability gap, not immediately.
- **Confusing practice management with program management** — a practice
  spans many concurrent projects/clients indefinitely with no defined end;
  a program (see [[program-management]]) is a bounded set of related
  projects working toward a specific benefit and then closing.

## Learn more

- [[program-management]], [[portfolio-management]] for the adjacent bounded-work and cross-portfolio disciplines.
- [[united-kingdom-government-digital-and-data-profession-capability-framework]] for a real, published discipline-capability framework a practice lead might use for career pathing.
- [[continuing-professional-development]] for the individual-practitioner development side a practice lead is often responsible for.