How we work
From Capability Priorities to Change in Practice
DhruvaLabs combines consulting, targeted development, real-work application and proportionate evidence so the response follows the problem—not the other way around.
The method is structured. The intervention is contextual.
The starting point
Begin With the Problem, Not the Programme
A performance issue may reflect a capability gap, a system constraint or both. Starting with a preferred intervention—training, coaching, assessment or organisational change—risks solving the wrong problem well.
DhruvaLabs first clarifies what is shifting, where performance is being constrained and what people or the organisation may need to become capable of doing differently.
The intervention should be a conclusion, not an assumption.
How we partner
Advise. Develop. Evidence.
Advise
Understand the business question, changing work and capability implications before deciding what intervention is required.
Develop
Build the capabilities the situation requires using the mechanisms most appropriate to the need.
Evidence
Examine what changed, where it showed up and what the organisation should do next.
This describes how DhruvaLabs partners with the organisation. The method below describes how the work progresses.
The method
Discover → Architect → Develop → Apply → Measure
Five stages create discipline without assuming that every engagement requires the same intervention, duration or level of assessment.
Stage 01 · Discover
What is actually changing?
Understand the business context, changing work, role expectations, people and organisational conditions before deciding what needs development.
Examine only what is relevant to the question.
Possible activities may include
- Executive conversations
- Role and work analysis
- Capability exploration
- Selected assessment where useful
- Existing organisational evidence
- Observation of relevant work or situations
Not every engagement requires all of these.
Typical decision
Where does the problem primarily sit—and is development actually the right first response?
Potential output
Capability priorities and problem definition
Where this is a standalone starting engagement, it routes to the Capability Transformation Blueprint.
Explore Capability Discovery →Stage 02 · Architect
What must become different?
Translate the business question into clear capability priorities, target populations, developmental responses and evidence of meaningful change.
Define capability priorities
What must people, leaders or the organisation become better able to do?
Match development to the need
Which mechanisms are appropriate—and which are unnecessary?
Define application
Where should the capability show up in real work?
Define evidence
What would give the organisation reasonable confidence that meaningful change occurred?
Define change before claiming change.
Stage 03 · Develop
How should the capability be built?
Development is matched to the nature of the capability rather than delivered through one default format.
In practice
- Knowledge may need teaching.
- Skill needs practice and feedback.
- Judgment needs Decision Practice & Review.
- Behavioural patterns may need coaching.
- Professional perspective may benefit from mentorship.
- System constraints may require changes around the person.
Stage 04 · Apply
Can the capability survive contact with real work?
Development is taken into the decisions, conversations, professional situations and repeated behaviours in which capability actually matters.
Typical application may involve
- Live decisions
- Client or stakeholder conversations
- Professional work
- Leadership situations
- Team practices
- Repeated behavioural experiments
These are possibilities, not universal requirements.
Development matters when something changes in practice.
Stage 05 · Measure
What changed—and how do we know?
DhruvaLabs examines evidence proportionately to the decision being made rather than measuring everything because it can be measured.
Evidence may include
- Capability or judgment evidence
- Behavioural and application evidence
- Work evidence
- Mentor or manager observations where appropriate
- Relevant organisational indicators where a credible relationship exists
Measurement should help the organisation make a better next decision—not merely produce a score.
Typical next decisions may include
Continue, adapt, deepen, scale, address a system constraint, or stop.
Not sure what stage your organisation is at?
Start With the Question, Not the Intervention
Capability Discovery can establish what is changing, where capability matters and what should happen next.
Explore Capability Discovery →Matching the response
Different Problems Require Different Forms of Development
The mechanism follows the developmental need.
Teach
Build relevant knowledge and understanding.
Practise + Feedback
Repeated execution, observation and recalibration.
Decide + Review + Recalibrate
Work through ambiguous situations, examine reasoning and improve decision quality.
Coach
Build awareness, experiment with alternatives and strengthen sustained behaviour change.
Mentor
Use experienced guidance, contextual interpretation and professional perspective.
Change the Conditions
Address relevant roles, norms, decision rights, processes or other system conditions.
More than one response may be appropriate when the problem spans multiple levels.
More development activity is not necessarily better development.
The objective is to use the least complexity necessary to create meaningful change.
Capability in context
The Person Is Only One Part of the Performance System
Capability may sit within the person, the demands of the role, the team around them or the wider organisational system. Effective development requires knowing which context matters to the problem.
Person × Role × Team × System
Person
Patterns, judgment, regulation, learning, relationships and agency.
Role
Professional demands, expertise, decisions, responsibilities and the situations in which value is created.
Team
Leadership, norms, coordination, feedback, trust and local ways of working.
System
Strategy, decision rights, processes, incentives, culture and organisational conditions.
Not every engagement examines all four with equal depth. We look at what is necessary to answer the question.
Our development philosophy
Develop the Person in Relation to the Work
Cognition, emotion, identity, behaviour, relationships, professional capability and organisational context can influence one another. DhruvaLabs takes an integrative view without assuming that every dimension requires intervention.
We develop the person in relation to the work—not apart from it.
Explore What We Transform →From development to work
Capability Has to Show Up Somewhere
Development becomes meaningful when it changes how people approach consequential situations in their work.
Decisions
How people interpret information, make trade-offs and exercise judgment.
Conversations
How leaders, professionals and teams communicate, challenge, influence and give feedback.
Professional Work
How expertise, skills, tools and judgment are applied to produce value.
Team Practices
How capability is reinforced—or undermined—through repeated ways of working.
Application is designed into development rather than treated as a post-programme hope.
Evidence of change
From Assumption to Evidence
Every intervention begins with assumptions about what should change. The real question is whether the expected change materialised in practice.
Define change before claiming change.
Did Capability Change?
Is there credible evidence of change in relevant knowledge, skill, judgment, behavioural patterns or professional capability?
Did It Reach the Work?
Did that change appear in decisions, conversations, professional practice, repeated behaviour or team ways of working?
Did It Matter?
Where appropriate, is there evidence that the change contributed to something the organisation values—such as quality, reduced rework, faster competence, client value, managerial leverage or execution?
The stronger the claim, the stronger the evidence should be.
We distinguish between evidence of development, evidence of application and evidence of business relevance. They are related, but they are not the same thing. Where a business outcome is involved, we describe the relationship honestly rather than claiming direct causal attribution.
Developmental integrity
Trust Is Part of the Intervention
People engage differently with development when they understand why information is being collected, how it will be used and what remains private.
Purpose Before Assessment
Collect only what is relevant to the developmental question.
Developmental Confidentiality
Private reflection and coaching content should not quietly become organisational performance data.
Participant Agency
People should understand the purpose, boundaries and use of developmental information.
Appropriate Scope
Developmental work is not clinical diagnosis or covert performance appraisal.
Clinical concerns sit outside the scope of developmental intervention and should be handled through appropriately qualified routes where relevant.
Clear Expectations Before the Work Begins
Engagement Contract
What the organisation is trying to change and how the work will operate.
Evidence Contract
What evidence will be considered and what claims that evidence can reasonably support.
Developmental Confidentiality Contract
What information remains private, what may be aggregated and what the organisation will receive.
These are operating agreements that establish clarity, not legal documents.
How engagements can grow
Discover. Prove. Scale.
This is the commercial progression of an engagement. It is separate from Discover → Architect → Develop → Apply → Measure, which describes how the capability work itself progresses.
Discover
Clarify the capability question and determine what should happen next.
Typical starting point: Capability Discovery.
Prove
Apply the approach to a focused population, role or business problem and examine whether meaningful change occurs.
Scale
Extend what has demonstrated value while adapting it to additional populations, roles or contexts.
Scale should follow evidence, not enthusiasm.
Where to begin
You Do Not Need to Know the Intervention Before the Conversation Begins
If the capability question is clear, we can discuss the appropriate response. If it is not, Capability Discovery can help determine where the problem sits and what should happen next.