Maintaining Objectivity in Reports

Most people think neutrality and objectivity are the same thing. If you believe that... you're missing the point entirely. A client recently asked me to review a valuation report that had cost them a potential acquisition deal. The report looked professional, had all the right numbers, and followed industry standards perfectly. But something felt off about the conclusions. The Valuer had taken a completely neutral approach - presenting market comparables without any deeper analysis or professional judgment. But neutrality isn't objectivity, and that distinction cost my client dearly. Neutrality is surface-level reporting. Objectivity is evidence-based insight. Neutrality means you don't take sides. You simply report numbers as they are, without bias. It sounds safe - but it often leads to shallow analysis that misses critical factors. Objectivity goes much deeper. It means tying every conclusion to evidence, even when the outcome is inconvenient for the client. Objectivity requires professional reasoning that connects assumptions, market realities, and risks into actionable insights. Let me show you the difference with a real example. Suppose you're valuing an industrial facility for a potential acquisition. A neutral report might say: "Here is the market value based on comparable assets." An objective report digs further: "While the comparables suggest this value, regulatory hurdles and outdated machinery reduce true viability. The adjusted range is lower, and here's the evidence to support it." The difference? Neutrality presents figures. Objectivity presents truth. And truth, even when uncomfortable, is what lenders, investors, and courts actually rely on. I've seen too many deals fall apart because someone confused being neutral with being objective. They thought avoiding difficult conversations would protect relationships, but it just delayed the inevitable problems. The businesses that succeed in today's market don't want sugar-coated reports. They want insights they can act on, even if those insights challenge their assumptions. That's why in my experience, neutrality produces numbers. But objectivity produces the insights that drive real business decisions.

𝗪𝗲 𝘁𝗿𝘂𝘀𝘁 𝗼𝘂𝗿 𝗠𝗜𝗦 𝗿𝗲𝗽𝗼𝗿𝘁𝘀. After all, they’re “𝘥𝘢𝘵𝘢-𝘥𝘳𝘪𝘷𝘦𝘯,” right? But here’s the uncomfortable truth: 𝗘𝘅𝗰𝗲𝗹 𝘀𝗵𝗲𝗲𝘁𝘀 𝗰𝗮𝗻 𝗯𝗲 𝗯𝗶𝗮𝘀𝗲𝗱... 𝘀𝗼𝗺𝗲𝘁𝗶𝗺𝗲𝘀 𝘀𝘂𝗯𝘁𝗹𝘆, 𝘀𝗼𝗺𝗲𝘁𝗶𝗺𝗲𝘀 𝗱𝗮𝗻𝗴𝗲𝗿𝗼𝘂𝘀𝗹𝘆. ➡️ 𝘚𝘦𝘭𝘦𝘤𝘵𝘪𝘷𝘦 𝘒𝘗𝘐s: Highlighting only the “feel-good” metrics while ignoring the ones that reveal cracks. ➡️ 𝘊𝘩𝘦𝘳𝘳𝘺-𝘱𝘪𝘤𝘬𝘦𝘥 𝘵𝘪𝘮𝘦𝘧𝘳𝘢𝘮𝘦𝘴: A report may look stellar if you show Q2, but not so much if you include Q1. ➡️ 𝘏𝘪𝘥𝘥𝘦𝘯 𝘧𝘪𝘭𝘵𝘦𝘳𝘴 𝘪𝘯 𝘗𝘪𝘷𝘰𝘵𝘛𝘢𝘣𝘭𝘦𝘴: A simple unchecked box can completely skew the story your data is telling. These aren’t just harmless quirks. They can 𝗱𝗶𝘀𝘁𝗼𝗿𝘁 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗿𝗲𝗮𝗹𝗶𝘁𝘆, leading to wrong calls. Whether it’s approving budgets, launching products, or restructuring teams. So, how do we keep reports honest? ✅ Cross-check KPIs against original objectives. ✅ Review multiple time horizons, not just the “best-looking” ones. ✅ Audit filters and slicers before presenting. ✅ Encourage a culture where bad news is not buried, but acted upon. Because at the end of the day, data doesn’t lie... but reporting can. The real question is: 𝘈𝘳𝘦 𝘸𝘦 𝘳𝘦𝘢𝘥𝘺 𝘵𝘰 𝘤𝘰𝘯𝘧𝘳𝘰𝘯𝘵 𝘵𝘩𝘦 𝘸𝘩𝘰𝘭𝘦 𝘵𝘳𝘶𝘵𝘩? 👉 𝙃𝙤𝙬 𝙙𝙤 𝙮𝙤𝙪 𝙚𝙣𝙨𝙪𝙧𝙚 𝙣𝙚𝙪𝙩𝙧𝙖𝙡𝙞𝙩𝙮 𝙖𝙣𝙙 𝙩𝙧𝙖𝙣𝙨𝙥𝙖𝙧𝙚𝙣𝙘𝙮 𝙞𝙣 𝙩𝙝𝙚 𝙧𝙚𝙥𝙤𝙧𝙩𝙨 𝙮𝙤𝙪 𝙬𝙤𝙧𝙠 𝙬𝙞𝙩𝙝? #DataDrivenDecisionMaking #DataAnalytics #ExcelReports #DataTransparency #MISReporting

🧠 CIA Daily Drill #020 The “Relationship Pressure” Trap 📌 CIA Syllabus: Part 1 – Domain 2: Ethics & Professionalism Part 2 – Domain 4: Communicating Results & Monitoring Progress Part 3 – Governance & Organizational Relationships 🎯 QUESTION OF THE DAY During a final audit discussion, management strongly disagreed with several significant audit observations related to weak procurement controls and inadequate monitoring activities. The audit manager believed the observations were properly supported by sufficient audit evidence. However, the audit manager also knew that the auditee executive had a close relationship with senior leadership and could negatively influence future support for the internal audit function. To avoid conflict, a senior member of the audit team suggested softening or removing some observations from the final report. What is the BEST action for internal audit management to take? A. Modify or remove the observations to preserve a positive working relationship with senior management B. Delay issuing the report until management becomes more cooperative and accepting of the observations C. Maintain the observations if they are properly supported, while communicating them objectively and professionally D. Escalate the disagreement immediately to the board because management disagreement automatically impairs audit independence 🧠 KEY INSIGHT ⚠️ This is a “relationship pressure vs audit integrity” judgment trap - Internal audit effectiveness depends on credibility, objectivity, and evidence-based reporting - Strong relationships with management should not influence audit conclusions or suppress supported observations - Professional disagreement does not automatically require escalation if observations are adequately supported and communicated appropriately - Auditors must balance professionalism and diplomacy without compromising independence or integrity 👉 Internal audit protects its long-term credibility by reporting supported issues objectively, even under political pressure. 📌 CORRECT ANSWER: C ✔ Preserves audit integrity and objectivity ✔ Relies on sufficient and appropriate evidence ✔ Maintains professional communication standards ✔ Avoids inappropriate influence from organizational relationships ❌ WHY OTHERS FAIL A → Relationship concerns should not override supported audit conclusions B → Delaying reporting does not resolve objectivity or governance concerns D → Disagreement alone does not automatically require escalation to the board 🧩 MEMORY ANCHOR 👉 Good relationships should improve communication, not weaken audit conclusions. 📢 Follow for advanced CIA drills focused on audit judgment, governance pressure, organizational politics, and real-world internal audit dilemmas. #CIAExam #InternalAudit #AuditJudgment #Governance #ProfessionalSkepticism #AuditReporting #CIAExamPrep

Lesson Learned: "Don't Drink Client's Bathwater" As a consultant, have you ever found yourself so immersed in developing solid client relationship that you started seeing the world through their eyes? During my consulting days, I had an experience that reminded me of the importance of maintaining an objective perspective, no matter how compelling a client's narrative might be. I was working with a mining client (my first project) where we were trying to optimise cost of operations. My client was passionate, driven, and had deep expertise in the domain, naturally, it created an amazing impression in my mind and I found myself wholeheartedly buying into their narrative / perspective, advocating for their judgement without questioning it. But then, reality hit. 🚨 We started noticing discrepancies between their performance and the market benchmarks. We were nowhere near the benchmarks. It became clear that in my eagerness to support the client, I had overlooked critical signs and failed to challenge their assumptions. Here are three key takeaways from this experience: 1️⃣ Maintain Objectivity: While it's important to support your client, it's equally important to provide honest, objective feedback based on data and market insights. 2️⃣ Challenge Assumptions: Don’t be afraid to question and challenge your client constructively. This isn’t about being negative but about ensuring that the strategy is grounded in reality. 3️⃣ Stay True to Data: Let data be your guide. In the end, facts and figures should drive decisions. Ensure that your ideas are data-backed and not solely based on someone's "experience". This experience was a valuable reminder that while it's important to be passionate and supportive, we must also remain critical thinkers and advisors. "Don't drink client bathwater" means keeping your objectivity intact and ensuring that you're always providing the best possible guidance to your clients. Has anyone else experienced something similar? How do you balance supporting your client with maintaining objectivity? Let's discuss! 💬 #ClientManagement #ConsultingLife #ProfessionalGrowth

📜 🖇 Report writing is the window into your competence as an investigator and a potential goldmine of opportunities for those looking to raise doubt about your competence or even your integrity as an investigator. None of us wants to have our work characterized as poor, biased, unfair, or incompetent simply because we didn't manage our writing and ensure it stood up to review. It isn't about winning a Giller or Pulitzer prize, but it needs to be solid. Here are a few red flags to avoid in your reports: 🚩 Unfocused Objectives: A well-defined mandate is critical to understanding the scope and nature of the investigation. This needs to be clearly stated at the outset of your report. 🚩Vague or Missing Methodology: An investigation is as much about your process as the outcome. Ensure you provide the investigation steps, including what you did and did not do. This helps readers understand your approach and will instill confidence, lending credibility to your process. 🚩 Loose Timelines: Understanding the timeline of complex issues or events is often crucial to readers grasping the nuances of what was investigated. Make this clear, and consider a visual aid for the timeline for complex matters. 🚩 Scant Evidence: In your efforts to support your findings, or in the case of professional regulatory investigations, instilling confidence in those charged with making decisions, ensure you have a proper overview of the evidence. Remember, evidence leads to conclusions, not the other way around. Be sure anyone reading your report will see the evidence and be able to draw the logical line from that evidence to a defensible conclusion. 🚩 Context Neglected: Don't lose sight of the context around a matter. Issues described in a vacuum can be misunderstood in terms of their significance. Consider legislation, broader policies, and industry standards where appropriate. Provide the backstory to help readers understand the bigger picture. 🚩 Unintended Signals of Bias: Bias can sneak up on you. Be vigilant about your own bias. It exists in all of us. Ensure your writing is impartial. Avoid the adjectives that add emphasis to a statement. It is better to say, "The evidence supports the Complainant's assertion that..." Rather than say, "The overwhelming body of evidence clearly and definitively supported the Complainant's assertion that..." 🚩 Jargon Overload: While we live in a technical world, remember to make your reports accessible to all readers by using clear and straightforward language. 🚩 Inadequate Review: Always double and triple-check your work, and if possible, have it reviewed by someone, not just for grammar and spelling but to ensure completeness, readability, and understanding. There is more, but not in 3000 characters! Let's get another dialogue started so we all learn from each other. #Investigation #ReportWriting #BestPractices

An established campaign should not be prioritized over a new test that is clearly delivering better results. Recently, we reviewed a Google/PMax account where newer asset groups within existing campaigns began outperforming the legacy structure. The performance difference was significant. The legacy asset group had a longer track record and felt safer due to its familiarity within the account. However, the newer assets demonstrated a much clearer positive trend. This does not mean making abrupt changes after only a day or two. New campaigns and asset groups require sufficient time, budget, and conversion data to demonstrate their effectiveness. At the same time, do not disregard positive results from new tests simply because the existing campaign has more history. This is why reporting windows are important. A 14-day reporting window may underrepresent new tests if the assets were not active for the entire period. A 7-day window can provide a clearer view of current momentum. Neither window offers a complete picture, so context is essential for accurate interpretation. Teams often become attached to campaigns that were previously successful. And I get it. History feels safe. However, factors such as product mix, creative assets, search behavior, promotions, and margins all change over time. What was effective six months ago may no longer be the best use of budget today. The practical approach is to avoid ending new tests prematurely and to refrain from supporting outdated structures out of habit. Evaluate the data objectively, review the appropriate reporting window, and ensure the test has sufficient budget. When the results are strong enough, allocate budget to what is currently performing best. Forget about preserving legacy campaigns, the real win is ensuring the account continues to progress in the right direction.

Why Incident Reporting Is a Critical Skill in Dubai’s Hospitality Security. In Dubai’s hospitality sector, incident reporting isn’t just paperwork — it’s a core part of safety, compliance, and guest trust. Every well-managed report protects your hotel’s reputation, supports investigations, and ensures full alignment with SIRA and Dubai Police requirements. Why It Matters 🔹 Legal protection — Clear, factual records support audits and investigations. 🔹 Operational clarity — Accurate documentation helps managers make fast, informed decisions. 🔹 Guest safety — Good reports highlight risks and trends and prevent repeat incidents. 🔹 Regulatory compliance — Hotels must record and report certain incidents to SIRA and Dubai Police. What Every Strong Incident Report Should Include ✔ Date, time & precise location ✔ Type of incident (medical, theft, fire alarm, system failure, etc.) ✔ People involved (guests/staff/witnesses) ✔ Immediate actions taken & timestamps ✔ Photographs, CCTV details & evidence collected ✔ Notifications made (Supervisor, Duty Manager, Police, SIRA) ✔ Clear, objective narrative — no opinions or assumptions ✔ Corrective actions & recommendations How Security Teams Should Handle Incidents — Step by Step 1️⃣ Ensure safety first — medical support, evacuation, securing the scene 2️⃣ Preserve evidence — CCTV export, photos, witness statements 3️⃣ Document facts quickly — within the same shift whenever possible 4️⃣ Escalate correctly — notify management & authorities when required 5️⃣ Follow up — investigation, root cause analysis, and preventive actions In Dubai, Professional Reporting = professional security. Hotels rely on security teams not only to respond but also to record incidents with precision, objectivity, and integrity. Good reporting strengthens compliance, supports decision-making, and protects what matters most: guest safety and brand reputation. If your security team masters incident reporting, your entire operation becomes stronger, safer, and more resilient.

Sometimes, as security professionals, we may face temptations to compromise our integrity, which can jeopardize our careers early on. Maintaining personal integrity is crucial for long-term success and credibility in this field. But how do we achieve this? It starts with 𝐚𝐝𝐡𝐞𝐫𝐢𝐧𝐠 𝐭𝐨 𝐞𝐭𝐡𝐢𝐜𝐚𝐥 𝐬𝐭𝐚𝐧𝐝𝐚𝐫𝐝𝐬. Follow industry codes of conduct and emphasize honesty, confidentiality, and fairness in every aspect of your work. 𝐓𝐫𝐚𝐧𝐬𝐩𝐚𝐫𝐞𝐧𝐜𝐲 is also essential; be open about your actions and decisions to avoid conflicts of interest and ensure that any potential issues are addressed. 𝐂𝐨𝐧𝐭𝐢𝐧𝐮𝐨𝐮𝐬 𝐞𝐝𝐮𝐜𝐚𝐭𝐢𝐨𝐧 plays a significant role in upholding integrity. Regular training helps you stay updated on the latest legal and industry standards, ensuring your practices remain ethical and relevant. 𝐀𝐜𝐜𝐨𝐮𝐧𝐭𝐚𝐛𝐢𝐥𝐢𝐭𝐲 reinforces your credibility; take full responsibility for your actions and promptly correct any mistakes. 𝐂𝐨𝐧𝐬𝐢𝐬𝐭𝐞𝐧𝐜𝐲 𝐢𝐧 𝐩𝐫𝐨𝐟𝐞𝐬𝐬𝐢𝐨𝐧𝐚𝐥𝐢𝐬𝐦 is necessary. Treat everyone with respect and handle sensitive information with care, directly linking to the need to respect privacy. Protect confidential information diligently to uphold individuals' privacy rights. In investigations and assessments, 𝐢𝐦𝐩𝐚𝐫𝐭𝐢𝐚𝐥𝐢𝐭𝐲 is key. Ensure your judgments are free from personal biases or relationships. When it comes to reporting, maintain integrity by providing accurate and truthful information without any manipulation. 𝐄𝐭𝐡𝐢𝐜𝐚𝐥 𝐮𝐬𝐞 𝐨𝐟 𝐭𝐞𝐜𝐡𝐧𝐨𝐥𝐨𝐠𝐲 is another critical aspect. Follow legal and ethical guidelines when using surveillance and investigative tools to safeguard privacy and data security. Lastly, 𝐚𝐥𝐰𝐚𝐲𝐬 𝐫𝐞𝐬𝐩𝐞𝐜𝐭 𝐥𝐞𝐠𝐚𝐥 𝐛𝐨𝐮𝐧𝐝𝐚𝐫𝐢𝐞𝐬 by operating within the law and ensuring your actions are legally compliant. By focusing on these principles, you can effectively maintain personal integrity and build a trustworthy and successful career in the security and investigation industry.

Day 3: The Art of Incident Report Writing That Communicates Clearly and Protects Your Organization. Series: Security Operations – Beyond the Basics An incident report is more than paperwork — it’s a legal document, a communication tool, and your shield in case of scrutiny. Poorly written reports can hurt your team’s credibility. Clear, professional reports protect your organization and your people. Let’s break it down: What Makes a Strong Incident Report? 1. Accuracy Stick to the facts. Avoid assumptions, emotions, or guesses. Example: Say “Mr. Smith appeared intoxicated,” NOT “Mr. Smith was drunk.” 2. Clarity Use plain, direct language. Short sentences. Logical structure. Avoid jargon unless necessary and commonly understood. 3. Chronological Order Tell the story in the order it happened. Use time stamps: “At 14:05, I received a radio call...” “At 14:10, I arrived on the scene…” 4. Who, What, When, Where, Why & How Cover all the basics: Who was involved? What happened? When did it occur? Where did it happen? Why (if known)? How did it happen? 5. Professional Tone No jokes, no slang, no blame. Be respectful and objective — even if the situation was tense or emotional. Pro Tips: ● Use active voice: “I observed” instead of “It was observed” ● Attach evidence: CCTV footage, witness statements, or photos ● Proofread: Typos and grammar issues can damage credibility ● Sign and timestamp every report Real-World Impact: A well-written report: ● Helps management make informed decisions ● Supports disciplinary actions (if necessary) ● Can stand up in court or insurance claims ● Enhances your reputation as a thorough and professional officer Next up: We’ll talk about what makes a solid security audit — and how to run one that truly adds value. What’s the most important thing you were taught about writing incident reports? Drop a tip in the comments! #SecurityOperations #IncidentReporting #SecurityLeadership #LossPrevention #SecurityTraining #HospitalitySecurity #LinkedInSeries #BeyondTheBasics

Evaluator Positionality: The Lens We Bring to Work In M&E practice, data is our focus, and because of this, we often boast about objectivity, sometimes blindly assuming that we, the evaluators, are neutral instruments of truth. But in my experience, I've come to learn that we are hardly ever neutral. Yes, quality data should be devoid of bias, but the humans who collect and use it rarely are. 𝐖𝐞 𝐛𝐫𝐢𝐧𝐠 𝐨𝐮𝐫 𝐢𝐝𝐞𝐧𝐭𝐢𝐭𝐢𝐞𝐬, 𝐨𝐮𝐫 𝐭𝐫𝐚𝐢𝐧𝐢𝐧𝐠, 𝐨𝐮𝐫 𝐚𝐬𝐬𝐮𝐦𝐩𝐭𝐢𝐨𝐧𝐬, 𝐚𝐧𝐝 𝐞𝐯𝐞𝐧 𝐨𝐮𝐫 𝐛𝐥𝐢𝐧𝐝 𝐬𝐩𝐨𝐭𝐬 𝐢𝐧𝐭𝐨 𝐞𝐯𝐞𝐫𝐲 𝐦𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 𝐨𝐫 𝐞𝐯𝐚𝐥𝐮𝐚𝐭𝐢𝐨𝐧 𝐚𝐜𝐭𝐢𝐯𝐢𝐭𝐲 𝐰𝐞 𝐜𝐨𝐧𝐝𝐮𝐜𝐭. This is what evaluator positionality is all about: 𝐭𝐡𝐞 𝐫𝐞𝐜𝐨𝐠𝐧𝐢𝐭𝐢𝐨𝐧 𝐭𝐡𝐚𝐭 𝐰𝐡𝐨 𝐰𝐞 𝐚𝐫𝐞 𝐬𝐡𝐚𝐩𝐞𝐬 𝐡𝐨𝐰 𝐰𝐞 𝐬𝐞𝐞. Whether it's our gender, class, ethnicity, language, or lived experience, these factors influence: - What questions do we ask? - How we interpret responses. - Whose voices we amplify. - And sometimes, whose voices we unintentionally silence. I recall a specific project that involved a focus group discussion. I co-facilitated. When we collected the data, the silent consensus was that the FGD participants did not say what we expected them to say. In hindsight, I realized we were interpreting the participants' truth and lived experiences as disinterest or hesitation. We may be correct, but what was actually happening was a matter of our positionality. As I curate this post, that experience reminds me that data, as quality as it may seem, may carry some bias based on the evaluator's characteristics. Thank God I found a scientific explanation for those moments: evaluator positionality. Consequently, I am making a conscious choice to always: - Reflect on my own biases before and after each session. - Include local voices in the design and facilitation process. - Use peer debriefs to challenge my interpretations and refine them. - And where possible, include a reflexivity section in my reports. Evaluator positionality isn't a weakness. It's a strength when acknowledged. It's what makes our work more ethical, more inclusive, and more honest. So I'm curious: How do you manage your own positionality in your evaluation work? You can share tools, stories, experiences, and reflections.👇 Over the next couple of days, I will be sharing more on this subject, and I hope we all learn something from it as a community. Do well to repost this to your network, and let's connect Ngwoke Ifeanyi