Structured Engineering Dialogue: Mastering the CEDAR® Feedback Model

Framework Trademark & Collaboration Notice:
The CEDAR® Feedback Model is a registered trademark created by Anna Wildman. This instructional text and guidance framework have been revised and published in direct collaboration with Anna Wildman. For official guidance, books, workshops, and comprehensive training resources directly from the creator, please visit the official Oil in the Engine - CEDAR® Feedback Portal ↗. Empowering Engineers UK provides this interactive workspace as an independent educational tool to assist technical candidates in contextualising their leadership dialogues against UK registration standards.

Welcome to Empowering Engineers UK. Deploying the CEDAR® Feedback Model forms an absolute cornerstone of Our Mission to democratise premium engineering mentorship, enabling developers and technical professionals to successfully overcome the structural challenges encountered within The Mentorless Maze of modern industrial asset development. In complex engineering infrastructure programmes, high-tier manufacturing operations, and strict multidisciplinary environments, maintaining continuous professional alignment across all team levels is a primary metric of operational success. Engineering leads, technical managers, and project directors frequently face the challenging responsibility of correcting project drift, structural design errors, or workflow inefficiencies on site. Delivering vague, unstructured performance feedback loops often triggers personal defensiveness, masks systemic project liabilities, and ultimately compromises long-term team performance. In addition, a critical part of every leader's role is to support continual progress and motivation through positive feedback. To address these operational priorities, the Engineering Council standard for professional registration (UK-SPEC) establishes clear personal management requirements under Competence C (Responsibility, management, or leadership) and Competence D (Communication and interpersonal skills), demanding that registered professional engineers demonstrate a structured, repeatable capability to lead diverse teams, resolve technical disputes, and guide professional development pipelines cleanly.

The CEDAR® Feedback Model provides a structured and effective framework for those conversations. Importantly, it is the only feedback model that is fully collaborative, providing a rigorous step-by-step approach specifically designed to transform performance feedback and reviews. Developed from thousands of real-life conversations in over 40 countries, it guides an objective, action-oriented approach that supports positive action, even when those discussions involve difficult issues or corrective action. It ensures that graduate engineers and technicians take active personal ownership of their career growth. It also makes for stronger working relationships and reduces stress on both sides.

The five CEDAR steps are Context, Examples, Diagnosis, Action, and Review. Each step plays a vital part in the conversation. Together they ensure that no matter how concerned or anxious a leader may feel, the conversation is productive every time.

Deconstructing the Five Steps of a CEDAR® Performance Dialogue

Context [C]

The first step is to set the context jointly, to clarify how important the feedback is, and how it fits into overall performance. Without this perspective, information is a free-floating fragment, and it can be difficult to understand its significance. This establishes the approach as one of mutual understanding and investigation.

Whether the feedback is positive or developmental, anchor it within the bigger picture:

Expert Tip: When introducing positive feedback, explain the value their achievement brings to the goal. This encourages repeated action and fosters a sense of progress. When introducing developmental feedback, focus on the task, not the person. Instead of saying, "Here are your behaviours", say something like, "Let's look at the challenges with this task". For example, these may be with the baseline parameters, compliance guidelines, or design constraints where the variance happened. To satisfy UK-SPEC criteria, you must connect the performance gap directly to broader project impacts. For example, clarify how an unchecked calculation script or delayed drawing approval caused schedule drift, introduced capital expenditure liabilities, or expanded safety risks under CDM 2015 regulations.

Examples [E]

Once the context is clear, add specific examples to illustrate the situation clearly. The more this is grounded in hard facts, the easier it will be for the coachee to understand the specifics. In many cases, they will identify these examples for themselves. This step may cover a single substantial example or two or three smaller ones grouped together.

Diagnosis [D]

Next analyse why these results are where they are. Understanding the reasons behind performance is essential to learning, whether the feedback is about an area of strength or a gap.

Insight can sometimes be buried in the subconscious. The more it is possible to take a deliberate and reflective approach here, the more it will help the coachee make connections and create valuable "aha" moments. To facilitate insight and encourage a clear diagnosis of the specific situation or performance anomaly, ask open questions such as:

Action [A]

Up to this point the conversation has built awareness; the next step is for the coachee to apply that understanding and decide what actions will be important going forward. Unless the coachee is inexperienced in their role, always encourage them to lead this step. The leader's purpose as far as possible is to facilitate, not to dictate action. Coachees are also far more likely to implement actions that they have chosen for themselves. Encourage them to be as concrete as possible. The more they can visualise the difference between where they are now and where they are aiming, the easier it is to see how to achieve it.

For both positive feedback and corrective action, this may involve additional training modules, revised design workflows, or new script validation, effectively turning the plan into a permanent continuous professional development (CPD) log. In some instances, the individual might not know what to do, or you may need to be more directive. When this happens, add your suggestions, just do not do this too early. Coachees will stay silent if you offer your ideas too soon. Ask questions like:

Review [R]

Conclude the discussion by collaboratively agreeing on a concrete review schedule to support and track progress. Ask the coachee for their preferred timetable first, as this helps to understand how quickly they perceive they can take action, and also gives them a greater sense of control. If an alternative date is needed, explain why. Ask questions like:

Before the first review, provide positive and timely support, including opportunities to practice skills in day-to-day work. Lasting change only happens when behaviours move from deliberate actions to unconscious habits, and leadership support is crucial. When meeting up, give recognition for effort as well as tangible progress, and troubleshoot any outstanding issues.

Summary and Professional Registration Alignment

By breaking down vague and one-sided feedback into a collaborative, task-focused, and forward-looking discussion, CEDAR® feedback eliminates the ambiguity that frequently stalls graduate career progression inside high-pressure environments. Rather than facing a vague instruction to "improve project visibility" or "take ownership of design assets", the candidate can focus on highly targeted steps, such as setting up a spreadsheet to track active pipeline delivery paths or optimising simple layout script parameters. Having contributed fully to the plan, they are far more likely to own it.

This transparent approach builds mutual trust, encourages regular dialogue across team lines, and ensures that professional development remains steady, verifiable, and protected against shifting corporate constraints. Documenting these collaborative reviews provides clear evidence of proactive talent cultivation, helping candidates demonstrate the advanced team governance skills reviewed during formal chartership boards for Chartered Engineer (CEng), Incorporated Engineer (IEng), and Engineering Technician (EngTech) registrations.

For leaders, documenting these structural leadership interventions within your private digital logs provides formal Professional Engineering Institution (PEI) review panels with robust proof that you execute your personnel management duties with high commercial awareness, absolute technical objectivity, and a clear commitment to operational excellence.

Document your long-term career goals within your Development Action Plan (DAP), structure narrative evidence using the STAR Methodology, prepare for your Professional Review Interview (PRI), follow our latest updates on our official LinkedIn Company Page, and subscribe to our educational YouTube Channel.

CEDAR® Feedback System

Performance Dialogue & Management System (Author: Anna Wildman)

Set the context jointly. Clarify importance, impact level, and explore coachee's perspective.
e.g. Discussed overall scope of Line 2 hydraulic motor project and its downstream impact on site safety and plant uptime.
Ground in specific, objective, fact-based illustrations. Avoid overwhelm (maximum 4 examples).
e.g. Pointed out that the finite element model omitted dynamic wind load parameters mandated by Eurocode 3.
Analyse why results are where they are (strengths or gaps). Ask open questions to facilitate insight.
e.g. Asked: "What's behind this do you think?" Coachee identified gap in shift handover checklist guidelines.
Facilitate coachee-led concrete actions and indicator milestones. Focus on solutions and CPD logging.
e.g. Coachee committed to completing the advanced structural loading module and re-verifying calculation sheets.
Agree on a concrete review schedule and leadership support. Ask for coachee's preferred timetable.
e.g. Agreed follow-up check every Friday at 10:00 to recognize progress and review calculation scripts.