METHOD
CMDR works like a diagnostic practice for organizations. The method starts with reported symptoms, examines the evidence, identifies what matters, and recommends only the next step the condition justifies.
How CMDR does it.
Investigation before recommendation.
CMDR starts by understanding the condition before recommending a fix. The method identifies what is happening, why it matters, and what should happen next.
Evidence before assumption.
Findings are based on observed conditions, available evidence, and the people closest to the work.
Proportional Investigation.
The assessment goes only as deep as needed to support a responsible decision.
Practical next steps.
The result is a clear path forward: what to address, what can wait, and who should be involved.
CLARIFY
Start with the concern as it is being experienced.
Most organizations know something is costing them. Fewer can say exactly what, or where it started. That's normal. Finding the cause is part of the work. CMDR begins with the problem your organization can see or feel, then clarifies what needs to be investigated before conclusions are drawn.
Some problems have one clear cause. Others come from smaller issues that reinforce each other over time: unclear ownership, outdated information, process gaps, or systems that no longer match the work.
You do not need to know the cause before beginning. Finding the cause is part of the assessment.
The first step is to determine:
• What is happening
• Who is affected
• What has already been tried
• What information is needed
• What decision the assessment should support
CMDR confirms:
• The presenting concern
• Relevant stakeholders
• Scope and objectives
• Confidentiality requirements
• Information and access needs
• Schedule and communication expectations
ASSESS
Examine the evidence connected to the problem.
CMDR reviews the agreed information, systems, representations, and working practices relevant to the assessment. Depending on scope, this may include:
Public evidence
Websites, search results, maps, directories, listings, structured data, and machine-readable information.
Internal evidence
Documentation, knowledge systems, process records, responsibility structures, and existing technology or vendor relationships.
Human evidence
Interviews, questionnaires, customer pathways, employee workflows, and the reported paths information moves through the organization.
DIAGNOSE
Map the connected conditions producing the problem.
CMDR compares reported symptoms with observable evidence and actual working practices. Some issues have a clear, isolated cause. Others emerge from a constellation of connected weaknesses.
For example, inconsistent location information, unclear service descriptions, conflicting structured data, and outdated listings may collectively make a business harder to find and understand.
The effects may then appear as poor-quality inquiries, misrouted calls, inefficient marketing spend, customer confusion, or reputational risk.
CMDR follows these relationships across teams, systems, and customer-facing operations rather than forcing the problem to remain inside the department or service category where it was first noticed.
PRIORITIZE
Determine what deserves attention and in what order.
CMDR compares reported symptoms with observable evidence and actual working practices.
Findings are organized by evidence, impact, urgency, effort, dependency, risk, and likely value.
CMDR identifies what can be corrected individually, what must be addressed together, where responsibility and ownership sit, and which issues may not justify further investment.
MAP NEXT STEPS
Turn findings into a practical path forward.
An assessment does not commit your organization to a large implementation project.
CMDR prepares an executive findings report and reviews the results with leadership. CMDR may support selected corrections, coordinate qualified specialists, or prepare a clear handoff for internal teams and existing vendors.
The report may include current-condition findings, priority risks, quick wins, target structural issues, recommended next actions, dependencies, responsible owners, and a detailed roadmap.
Once the findings are understood, the organization can decide what to act on, what can wait, what is not worth pursuing, and who should perform the work.
REASSESS
Confirm whether the condition has improved.
Where useful, CMDR establishes a baseline score, starting measures, or documented current state.
CMDR may support selected corrections, coordinate qualified specialists, or prepare a clear handoff for internal teams and existing vendors.
After improvements have been made, the organization can reassess the relevant condition to determine:
What changed
Whether the intended outcome was achieved
Whether new issues emerged
Whether further action is justified
The CMDR method
Designed to keep assessment work evidence-based, proportional, and useful. The goal is not to find every possible issue. The goal is to understand what is happening, identify what matters, and show what should happen next.
Evidence Before Assumption
CMDR does not assume the cause of a problem before investigation. Findings emerge from observed conditions, available evidence, stakeholder input, and the systems or documents connected to the work.
Practical Value Over Activity
The objective is not to create the largest possible project. CMDR focuses on work most likely to reduce friction, support decisions, or create meaningful value.
Proportional Investigation
Not every concern requires a deep internal assessment. CMDR investigates far enough to understand the issue, test the relevant conditions, and recommend an appropriate next step.
Connected Problems Require Connected Thinking
Business problems often cross departmental boundaries. CMDR examines relationships between public information, internal systems, people, documentation, and operating reality.
Capability Over Dependency
A successful engagement leaves the organization better informed, better equipped, and better able to act through its own team or trusted providers.
Assessment first.
Everything else follows from what it finds.
Start with what you are seeing. You do not need to know the cause before contacting CMDR. The first step is determining whether an assessment is useful, what scope makes sense, and what should happen next.
![](data:image/svg+xml,<svg display="block" role="presentation" viewBox="0 0 74 19" xmlns="http://www.w3.org/2000/svg"><g d="M 27.63 7.067 L 24.074 0.049 L 19.235 0.049 L 19.235 18.789 L 24.074 18.789 L 24.074 11.259 L 27.63 17.181 L 31.185 11.235 L 31.185 18.789 L 35.951 18.814 L 35.951 0.073 L 31.185 0.049 Z M 74 1.755 L 70.444 0 L 57.309 0 L 57.309 18.814 L 62.074 18.814 L 62.074 14.11 L 66.444 14.11 L 68.815 18.814 L 73.975 18.814 L 71.383 13.696 L 73.975 12.38 L 73.975 1.755 Z M 69.235 9.407 L 62.099 9.407 L 62.099 4.776 L 69.235 4.776 Z M 9.531 0 L 3.531 0 L 0 1.779 L 0 17.059 L 3.531 18.814 L 16.667 18.814 L 16.667 11.771 L 11.901 11.771 L 11.901 14.135 L 4.765 14.135 L 4.765 4.728 L 11.901 4.728 L 11.901 7.067 L 16.667 7.067 L 16.667 0 Z M 51.358 18.814 L 54.79 17.059 L 54.79 1.755 L 51.235 0 L 38.099 0 L 38.099 18.814 Z M 50.025 4.703 L 50.025 14.11 L 42.889 14.11 L 42.889 4.703 Z" fill="transparent" height="18.81355849448424px" id="eGTG1oCaW" transform="translate(0 0.095)" width="73.99999669818465px"><path d="M 27.63 7.067 L 24.074 0.049 L 19.235 0.049 L 19.235 18.789 L 24.074 18.789 L 24.074 11.259 L 27.63 17.181 L 31.185 11.235 L 31.185 18.789 L 35.951 18.814 L 35.951 0.073 L 31.185 0.049 Z M 74 1.755 L 70.444 0 L 57.309 0 L 57.309 18.814 L 62.074 18.814 L 62.074 14.11 L 66.444 14.11 L 68.815 18.814 L 73.975 18.814 L 71.383 13.696 L 73.975 12.38 L 73.975 1.755 Z M 69.235 9.407 L 62.099 9.407 L 62.099 4.776 L 69.235 4.776 Z M 9.531 0 L 3.531 0 L 0 1.779 L 0 17.059 L 3.531 18.814 L 16.667 18.814 L 16.667 11.771 L 11.901 11.771 L 11.901 14.135 L 4.765 14.135 L 4.765 4.728 L 11.901 4.728 L 11.901 7.067 L 16.667 7.067 L 16.667 0 Z M 51.358 18.814 L 54.79 17.059 L 54.79 1.755 L 51.235 0 L 38.099 0 L 38.099 18.814 Z M 50.025 4.703 L 50.025 14.11 L 42.889 14.11 L 42.889 4.703 Z" fill="rgb(207, 207, 207)" height="18.81355849448424px" id="N5G4hpbGt" width="73.99999669818465px"/></g></svg>)