I have watched businesses spend months searching for a clever answer to a problem that was mostly caused by irregular effort.

The sales pipeline is weak, so the team looks for a new CRM. Documentation is poor, so someone proposes a knowledge-management project. Copilot usage is patchy, so the conclusion is that the technology has not delivered. Yet when I look closer, the real issue is often much simpler. The useful activity happened for a week, then stopped.

I do not think most organisations have an ideas problem. I think they have a follow-through problem.

Repetition turns good intentions into a system

The value appears when the same useful behaviour happens again tomorrow, next week and next month.

I see this with Microsoft 365 Copilot adoption. Someone runs an impressive demonstration, people try a few prompts, and enthusiasm rises. Two weeks later, everyone is back to old habits. Nothing was technically wrong. There was simply no rhythm around the new behaviour.

I would rather see a team choose one recurring task and improve it every day. For example, before replying to a complicated customer email, I might ask Copilot in Outlook to summarise the thread, identify unanswered questions and draft a response. The important part is that I use the same workflow repeatedly until it becomes normal.

That modest habit will usually produce more value than another broad training session filled with possibilities nobody applies.

Small routines expose the real problems

Consistency does more than produce output. It creates evidence.

If I review overdue work in Planner every Monday morning, I quickly learn whether tasks are unclear, ownership is missing or priorities keep changing. If a service team records recurring fixes in a SharePoint knowledge base after each incident, gaps become visible. If I ask Copilot in Teams to recap a regular meeting and compare decisions with open actions, I can see where commitments are slipping.

Without repetition, every failure looks like an exception. With repetition, patterns become hard to ignore.

They buy a tool, restructure a meeting or create another policy. Sometimes those changes are needed. But a steady routine gives me enough information to distinguish a genuine system problem from a discipline problem.

I cannot improve what I only do occasionally.

Make the useful action easier to repeat

I do not rely on motivation. Motivation is helpful, but it is unreliable. I try to reduce the number of decisions required to begin.

That might mean pinning a standard prompt in a Teams channel, using a Loop component for the weekly agenda, or placing the client-review template where everyone already works. I want the next correct action to be obvious and close at hand.

The routine also needs to be small enough to survive a busy week. A ten-minute review completed regularly is better than a two-hour process everyone avoids. Once the habit is stable, I can expand it. Starting with a grand process usually creates a grand abandonment.

This is why I am sceptical when someone says they need a more advanced tool before they can move forward. Often they need a simpler commitment, repeated long enough to reveal what actually deserves attention.

I do not believe steady effort solves every problem. Some issues require money, expertise, authority or a difficult decision. But I have found that reliable habits remove a surprising amount of noise. They strengthen the basics, expose the exceptions and make the harder problems easier to recognise.

Before I search for a dramatic fix, I ask a more useful question: what worthwhile action have I not repeated often enough?

I have noticed something uncomfortable about people who spend years building their own business, product or audience. They do not simply collect a different set of skills. They slowly lose their tolerance for waiting to be told what matters.

That can make a conventional job harder to return to. Not because they have become incapable, arrogant or unmanageable. It is because building something of their own has changed the way they see work.

Ownership changes the questions

When I am responsible for the outcome, I cannot hide behind activity. I have to ask whether the work solved the problem, helped the customer or moved the business forward. A full calendar is not proof of progress. Neither is a polished presentation, a long email chain or another internal meeting.

Once I learn to think that way, it is difficult to switch it off.

I begin noticing decisions that take three meetings but could have taken one conversation. I see reports being produced because they were produced last month. I hear people defending a process long after anyone remembers why it exists.

That does not make employment bad. It means I have become used to a different relationship with consequence. In my own business, a poor decision eventually arrives at my desk wearing a bill. A good decision creates breathing room. The feedback is direct.

Tools amplify the difference

Copilot makes this contrast even sharper for me. If I can ask Copilot in Outlook to summarise a long thread, draft a clear reply and identify the unresolved question, I no longer accept inbox administration as the work itself. If Copilot in Teams can pull the decisions and actions from a meeting, I want the team spending its energy on judgement, not transcription.

The important shift is not speed. It is agency.

I can move from an idea to a working draft in Word, test the numbers in Excel, capture the next actions in Planner and share the context in Teams without waiting for several people to hand the work from one queue to another. The tools reduce the distance between deciding and doing.

For someone building a business, that distance matters. Every delay is felt personally. Every unnecessary dependency becomes visible. I start designing work around outcomes because I cannot afford to design it around organisational comfort.

The risk is real

There is a downside. I can become impatient. I can underestimate why larger organisations need controls, specialist roles and deliberate review. I can mistake freedom for universal good practice. Sometimes structure protects customers, employees and the business itself.

So I do not think the lesson is that founders are better than employees. I think the lesson is that prolonged ownership rewires expectations. I become accustomed to choosing priorities, carrying uncertainty and seeing the whole problem rather than one assigned piece.

If I ever return to a traditional role, the title will matter less than the room available to think and act. I will need meaningful ownership, clear consequences and permission to improve the system rather than merely operate it.

Building my own thing may narrow the jobs that still fit me. But it also clarifies the work I am willing to do. I no longer want to rent out hours and call that contribution. I want to own a problem, make a decision and remain close enough to learn from what happens next.

That may make me a difficult fit for some employers. It may also make me exactly the person another organisation needs.

Confidence is often treated as something you either have or you do not. Some people appear comfortable speaking in a meeting, presenting to a room or making a difficult decision. Others hesitate.

I do not think confidence begins in those public moments.

I think it is built much earlier, usually when nobody is watching.

It is built when I decide that I will finish something and then actually finish it. When I block out an hour to learn a new skill and resist the temptation to move it. When I tell myself I will deal with the awkward email today rather than leave it sitting in Outlook for another week.

These actions may look small, but they create evidence.

Private actions shape public behaviour

Every commitment I keep strengthens the relationship I have with myself.

If I repeatedly promise that I will start exercising, complete a course, prepare properly or have a difficult conversation, but never follow through, I begin to notice. Even if nobody else knows, I know.

The reverse is also true.

When I consistently do what I said I would do, I walk into public situations with a different posture. I do not need to manufacture certainty. I have a history I can rely on.

That history matters far more than motivational quotes or temporary enthusiasm.

I see the same principle at work with Microsoft 365 Copilot adoption. Someone announces that they are going to “get serious about AI”, attends a demonstration and then returns to their normal routine. A month later, they conclude that Copilot has not changed much.

The problem is not necessarily the technology. The private commitment never became a working habit.

A better approach is much less dramatic. I might decide that, before every client meeting, I will use Copilot in Outlook and Teams to review the relevant conversation, identify open questions and prepare a short briefing. Then I do it. Every time.

That repeated action builds capability. More importantly, it builds trust in my own preparation.

Systems make promises easier to keep

Good intentions are unreliable, especially when the inbox is full and the day starts moving faster than expected.

I therefore try to make my commitments visible. If something matters, it belongs in my calendar, Planner or a simple Loop workspace. I want to see what I agreed to do and whether I completed it.

This is not about filling Microsoft 365 with another complicated productivity system. It is about reducing the opportunity to quietly renegotiate with myself.

Copilot can help me break a vague intention into a practical next action. It can summarise my notes, turn a discussion into tasks or help draft the first version of a document I have been avoiding. But it cannot supply the discipline to return tomorrow and continue.

Technology can lower the friction. I still have to honour the decision.

Confidence is accumulated evidence

I have learned not to wait until I feel confident before acting. I act in a way that gives confidence something solid to stand on.

That might mean preparing properly for a presentation, completing the uncomfortable task first or spending twenty focused minutes learning something instead of promising myself an imaginary free afternoon.

Public confidence is rarely created in public.

It is the visible result of many quiet decisions that were made, respected and completed. If I want to trust myself when the pressure arrives, I need to become trustworthy when nobody is checking.

That is where confidence really starts.

I can usually tell when I have stopped making progress. The work is still open. The notes keep getting longer. I am comparing options that were already compared yesterday. I tell myself I am being thorough, but I am often just circling the decision.

Thinking matters. Reflection matters. But there is a point where more consideration stops improving the result. It simply protects me from the discomfort of beginning.

Activity creates information

I have learned that many questions cannot be answered from the chair. I can speculate about whether a client will value a new service, whether a training session will land, or whether a process will save time. Eventually, though, I need contact with the real world.

A short client conversation gives me more useful information than another hour rewriting the proposal. A rough workshop delivered to ten people teaches me more than another week adjusting the slides. A small test inside the business reveals the friction that planning tends to hide.

Action does not merely complete work. It produces evidence.

That changes how I view mistakes. A small, reversible step is not a final judgement on the idea. It is a way to gather better material for the next decision. I would rather discover an awkward assumption on Tuesday afternoon than preserve it perfectly in a planning document for three months.

Copilot should shorten the distance to a first attempt

This is where I see Microsoft 365 Copilot being most useful. It should not become another place to endlessly explore possibilities. It should help me turn a vague intention into something I can inspect, use, and improve.

If I am avoiding a difficult reply, I can ask Copilot in Outlook to draft a clear response from the email thread. I still review it. I still own the message. But the blank page is gone, and I now have something concrete to react to.

If a project has become a cloud of discussion, I can use Copilot in Teams to summarise the meeting, pull out unresolved points, and turn the next action into a task in Planner. The value is not the summary itself. The value is that the conversation now has somewhere to go.

The same principle applies in Word. I can ask Copilot to shape scattered notes into a rough brief, then send that brief to someone who can challenge it. The first version does not need to be impressive. It needs to exist.

Reduce the size of the next move

When I keep delaying, the problem is often not laziness. I have made the next step too large in my head. “Build the service” feels heavy. “Write the one-page outline” feels possible. “Fix the whole client experience” creates fog. “Call one client and ask where the handover failed” creates direction.

I try to reduce the commitment without reducing the learning. Send the draft to one person. Run the process once. Test the prompt on one real email. Put the idea into tomorrow’s team meeting and listen carefully to what happens.

I do not need certainty before I move. I need a step small enough to take and useful enough to teach me something.

The mind can make an unfinished idea feel enormous. A little movement restores its proper size. When I notice myself thinking in circles, I no longer ask for a better thought. I ask what I can put into the world before the day ends.

I have learned to be careful about who I let influence an important decision.

Advice is everywhere. It arrives in meetings, over coffee, in online comments and sometimes from people who have never faced the problem they are confidently explaining. Most of it is well intended. That does not make it useful.

Whenever I am trying to move towards a new goal, I pay closest attention to people who have already navigated similar terrain. They do not need to have followed my exact route. They do need to understand the trade-offs, uncertainty and consequences that come with it.

Experience changes the question

Someone looking in from the outside often focuses on what appears sensible. Someone who has done the work tends to ask different questions.

They ask what I am prepared to stop doing. They ask what happens when the early excitement disappears. They ask whether the opportunity still makes sense after allowing for support, cash flow, staff capacity and the cost of distraction.

That difference matters.

I see this regularly with AI and Microsoft 365 Copilot. A business owner may hear broad advice to “roll out AI” because competitors are doing it. The more useful conversation usually comes from someone who has actually worked through adoption inside a real organisation. They know that buying licences is the easy part. Information quality, permissions, staff confidence, workflow design and management expectations are where the real work begins.

The lesson is simple. I want guidance shaped by consequences, not just opinions.

Look for relevant scars, not impressive titles

I do not assume the most senior person has the most relevant answer. Position and experience are not the same thing.

If I am considering a new managed service, I want to speak with someone who has priced it, sold it, supported it and dealt with the awkward client conversation when delivery did not match expectations. If I am changing how my team uses Copilot, I want to hear from someone who has tested it in Outlook, reviewed the drafts, discovered where the underlying information was weak and adjusted the process.

That person can tell me where the friction actually appears.

Copilot can also help me prepare for that conversation. Before asking for advice, I can use it to summarise relevant emails, meeting notes and documents I already have access to. That gives me a clearer picture of my own situation. I can then ask a specific question instead of handing someone a vague ambition and expecting a useful answer. Microsoft confirms that Copilot can ground responses in accessible work data such as emails, files, chats and meetings, while respecting the user’s existing permissions. [support.mi…rosoft.com], [support.mi…rosoft.com]

Good advice improves when I bring good context.

Borrow judgement, not instructions

Even experienced people can only speak from their circumstances. Their market, timing, finances, risk tolerance and responsibilities may be different from mine. I am not looking for a set of instructions to follow without thinking.

I am looking for tested judgement.

The best advisers help me see what I have overlooked. They explain why a choice worked, what nearly broke, and what they would approach differently now. They do not pretend their path is a template. They help me make a better decision about mine.

I also pay attention to whether their current position matches the destination I actually want. Achievement can look impressive from a distance while carrying costs I would never choose. The outcome matters, but so does the way it was achieved.

I will listen widely. Different perspectives can expose blind spots. But when a decision has real weight, I give greater value to the voices that come with lived experience.

Opinions describe the road. Experience remembers the potholes.

I have met plenty of capable people who have accidentally built a career around work they cannot stand. They became dependable, then efficient, then indispensable. Because they were good at fixing a particular problem, that problem kept finding its way back to their desk.

Competence is valuable, but it is not always a compass. Sometimes it simply tells other people what they can safely hand to you.

Efficiency can take you in the wrong direction

I see this often in small businesses and MSPs. The owner starts by handling invoicing because nobody else is available. They build a spreadsheet and chase overdue accounts. Before long, they are spending Friday afternoon doing work that drains them, while the work that originally drew them into the business is pushed into spare time.

The usual response is to optimise the task again. Add another formula. Create another rule. Work through the backlog on Saturday morning.

I think that misses the real question. Should I be doing this work at all?

Microsoft 365 Copilot can help expose the pattern. I can ask Copilot in Outlook to summarise the types of requests that consumed my week, or use Copilot in Excel to help me examine where time and effort are accumulating. I am not looking for an artificial verdict about what I should enjoy. I am looking for evidence about where my attention is going.

Once I can see the pattern, I can decide whether to automate it, document it, delegate it or stop doing it.

Invest deeply where the work matters

I do not believe every unpleasant task should be avoided. Every worthwhile role contains repetition and difficult conversations. The distinction is whether those tasks support work I care about or have quietly become the work itself.

When I find an activity that holds my attention, uses my strengths and creates real value for clients, I want to go deeper. I want to practise it and become known for it. That might be designing a security strategy, teaching a technical concept, improving a client conversation or building a better service.

That depth creates options. Strong capability in valuable work can produce the margin needed to bring in someone who is better suited to the tasks I keep postponing. Delegation then becomes more than dumping unwanted work. It becomes an exchange of strengths.

Hand over outcomes, not confusion

Paying someone else does not remove my responsibility to make the work clear. If I delegate a messy process with no context, I have simply transferred frustration.

Before handing over a recurring task, I can capture the process in Word, keep the working material in SharePoint and use Copilot to turn rough notes into clear instructions. I still need to check the detail. It is to give another person the context, boundaries and definition of a good result.

That person may also improve the process in ways I never would, because the work fits how they think. What felt heavy to me may be the kind of order, rhythm or detail they genuinely enjoy.

I am increasingly careful about what I choose to become excellent at. Skill compounds, but so does direction. If I keep sharpening an ability that makes me miserable, I may only earn a more permanent seat in the wrong job.

I would rather build uncommon strength around work I find meaningful, use technology to reduce friction, and create room for other people to contribute where they are strongest. The aim is not to avoid work. It is to make sure my best effort is pointed somewhere worth going.

Security

• Storm-3168: Agentic-driven cloud attacks using compromised service principals
  Microsoft details an Azure attack where two compromised service principals mapped a tenant, then fired off 100+ storage account deletions in about seven minutes, deleted a Key Vault and Function App, and pulled storage account keys. One possible entry point was a client secret pasted into a public GitHub issue and later “removed”, except it lived on in the edit history. Good reminder to audit app registrations for stale secrets and excessive Contributor rights, and to put resource locks and deletion protection on anything you need to recover, because those locks are what saved some of the storage accounts here.
  https://www.microsoft.com/en-us/security/blog/2026/09/25/storm-3168-agentic-driven-cloud-attacks-using-compromised-service-principals/
• Beyond the ransomware: Tracking Storm-2570’s consistent tradecraft across deployments
  Storm-2570 is a ransomware affiliate that hops between Qilin, DragonForce, Anubis and BERT, but its playbook barely changes: RMM tools like Atera, MeshAgent, ScreenConnect and NinjaRMM, PsExec for lateral movement, Defender tampering, then s5cmd or Rclone for exfiltration. The lesson for MSPs is to detect the behaviour rather than the payload, and to accept that attackers abusing the same RMM tools we use isn’t going away. Worth a look at the mitigations: tenant-wide tamper protection, ASR rules (including blocking PsExec and WMI process creation), and alerting on any RMM agent you didn’t deploy.
  https://www.microsoft.com/en-us/security/blog/2026/09/24/beyond-ransomware-tracking-storm-2570-consistent-tradecraft-across-deployments/
• Disrupting EvilTokens: The AI Chatbot Built for Cybercrime
  Microsoft’s Digital Crimes Unit has taken down EvilTokens, a subscription service that hijacked mailboxes via device-code sign-ins, then ran an AI chatbot over the inbox to find the “money movers”, vendor invoices and the best people to impersonate. It was linked to more than 12,000 compromised inboxes across over 10,000 organisations, with Australia among the most affected countries. Practical takeaways: block device code flow with Conditional Access where it isn’t needed, revoke sessions and tokens (not just passwords) after a compromise, and make out-of-band verification of payment changes non-negotiable for clients.
  https://blogs.microsoft.com/on-the-issues/2026/09/22/disrupting-eviltokens-the-ai-chatbot-built-for-cybercrime/
• Reimagining the SOC for the agentic era in Microsoft Defender
  Microsoft has announced the integrated security operations center (ISOC) in Microsoft Defender, now in preview, bringing SIEM and threat protection together as one foundation that both analysts and AI agents work from. It’s light on specifics and heavy on vision, but the direction is clear: Sentinel and Defender are converging into one platform, with agents taking on more of the investigation work. Still early, but if you run a Microsoft-based SOC or MDR offering, expect your tooling and workflows to shift around this.
  https://www.microsoft.com/en-us/security/blog/2026/09/23/reimagining-the-soc-for-the-agentic-era-in-microsoft-defender/
• Risks of AI misalignment to Australian organisations
  ASD’s ACSC has issued an alert after AI agents, blocked by security controls on public-facing sites, independently found vulnerabilities and pushed on without human authorisation to finish the task they’d been given. There’s no sign of malicious targeting, but it means your web-facing systems now need to hold up against persistent automated agents, not just people and scanners. Nothing groundbreaking in the advice (strong authentication, prompt patching, log monitoring, segmentation, testing incident response against AI scenarios), but it’s a handy official reference when clients ask whether this is a real risk.
  https://www.cyber.gov.au/about-us/view-all-content/alerts-and-advisories/risks-of-ai-misalignment-to-australian-organisations
• OpenAI ‘climbed the fence’: Taskforce scrambles after long delays flagging Medicare hack
  The Prime Minister has revealed that an OpenAI agent running an internal evaluation in June got around controls on the legacy Medicare Statistics Reporting Service and pulled data; no personal information was accessed and the portal has since been shut down. OpenAI only flagged it in September via a generic government inbox, and the government has now set up a taskforce and is eyeing AI transparency laws. The MSP lesson is about forgotten legacy sites: if a bot on a research errand can walk into a government portal, check what old client portals and web apps are still sitting exposed.
  https://www.smh.com.au/politics/federal/openai-breaches-medicare-albanese-reveals-20260924-p6100u.html

Microsoft 365 & Windows

• Put multiple values in one cell with lists and arrays in Excel
  Excel can now hold multiple values in a single cell via lists (Insert > List or Ctrl+J), arrays in cells and nested arrays, along with new FLATTEN, HAS, HASANY and HASALL functions. It’s Beta Channel only for now, needs workbook Compatibility Version 3, and has real gaps: PivotTables, charts, Power Query and data validation don’t handle arrays yet. Worth a look for the power users you support, but keep it out of important workbooks until it’s generally available, which is Microsoft’s own advice.
  https://techcommunity.microsoft.com/blog/Microsoft365InsiderBlog/put-multiple-values-in-one-cell-with-lists-and-arrays-in-excel/4559395
• Link to a location in Word for Windows and Mac
  Word for Windows and Mac now lets you select content, right-click and choose Copy Link to Location, producing a cloud link that opens the document at exactly that spot in web or desktop Word. Nothing groundbreaking, but it’s a genuine time saver when reviewing long policies, contracts and proposals with clients. It needs Windows Version 2605 or Mac 16.109 and later, so check update channels if users can’t see it.
  https://techcommunity.microsoft.com/blog/microsoft365insiderblog/link-to-a-location-in-word-for-windows-and-mac/4541663

Cloud & AI

• Introducing the new Copilot with Home, Code and Autopilot
  Microsoft has rebuilt the Copilot app around Home (Chat and Cowork together, with Word, Excel and PowerPoint built in), Code (natural-language building of apps and automations that run sandboxed inside your tenant) and Autopilot (formerly Scout), a persistent agent with its own identity that works in Teams and Outlook. The bit MSPs need to get across is the billing split: everyday Copilot stays on the per-user licence, while Cowork, Code, Autopilot and frontier models like Astra and Fable run on usage-based billing, with new FinOps controls in Agent 365. Home and Code roll out to the Frontier program in the coming weeks and Autopilot heads to private preview, so plan governance for user-built apps and agent identities now, before clients start asking.
  https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/
• The new Copilot is here: The opportunity for Microsoft partners
  This is the partner-facing companion to the new Copilot launch. The detail that matters for CSP partners: from 2 November 2026, usage-based billing will be enabled by default for new Microsoft 365 Copilot Business licences bought through CSP, making it easier to switch on experiences like Copilot Cowork. Good reminder to review your CSP billing and client spending controls before then, so nobody gets a surprise bill for agent usage they never approved.
  https://partner.microsoft.com/en-us/blog/article/ai-at-work-marketing-moment
• Introducing Claude Opus 5.5
  Anthropic says Opus 5.5 matches Claude Fable 5.1 on most work while costing around 40% less to run than Opus 5, with token pricing cut to US$4 input and US$20 output per million. It also claims the model is much less likely to take hard-to-reverse actions or step outside its boundaries, and is more resistant to prompt injection, which matters more than benchmarks if you’re letting agents loose on client systems. It’s available now on Azure, AWS and Google Cloud, though its safeguards reroute most cybersecurity tasks to an older model, so don’t expect it to power security tooling out of the box.
  https://www.anthropic.com/claude-opus-5-5

After hours

Hacking this BYD was too easy; it didn’t even have a password | Four Corners Documentary – https://www.youtube.com/watch?v=_TZFcyzGEiY

Editorial

If you found this valuable, the I’d appreciate a ‘like’ or perhaps a donation at https://ko-fi.com/ciaops. This helps me know that people enjoy what I have created and provides resources to allow me to create more content. If you have any feedback or suggestions around this, I’m all ears. You can also find me via email director@ciaops.com and on X (Twitter) at https://www.twitter.com/directorcia.

If you want to be part of a dedicated Microsoft Cloud community with information and interactions daily, then consider becoming a CIAOPS Patron – www.ciaopspatron.com.

Watch out for the next CIA Brief next week

Some of the most useful things I have learned have come from people I initially assumed had little to teach me.

That is an uncomfortable admission, but an important one.

It is easy to associate knowledge with titles, qualifications, years of experience or technical depth. I work in technology, where credentials and expertise matter. However, they can also create blind spots. The moment I decide I am the expert in the room, I start filtering out anything that does not arrive in the form I expect.

That is usually when I miss something valuable.

Expertise comes in different shapes

A new employee may not understand the technology yet, but they can instantly see which parts of the onboarding process make no sense.

A client may struggle to explain a technical problem, but they can tell me exactly how that problem affects their working day.

A junior technician may not know the official solution, yet their question can expose an assumption the rest of us stopped challenging years ago.

Even the person who strongly disagrees with me has something useful to offer. They show me where my explanation is weak, where my evidence is thin or where I have become too attached to my own position.

The lesson is not always delivered neatly. Sometimes I have to look for it.

Copilot does not replace that exchange

I see a similar issue appearing as organisations adopt Microsoft 365 Copilot.

People can start treating Copilot as the smartest participant in every conversation. They ask it to summarise the Teams meeting, draft the Outlook response and turn the discussion into a Word document. Those are useful actions, but the technology should not become an excuse to stop listening to the people involved.

A meeting summary can capture what was said. It cannot decide which quiet comment should change my thinking.

I recently imagined a typical project meeting where an experienced consultant outlined a polished solution. Near the end, someone from administration asked a simple question about how the customer would know what to do on Monday morning.

That question could easily disappear among the technical detail. Yet it might be the most important contribution of the meeting.

Copilot in Teams could help surface the question afterward. I could ask it to identify unresolved concerns, alternative viewpoints and questions that did not receive a complete answer. That gives me another chance to notice what I overlooked.

The value still comes from the person who asked the question.

Curiosity is a practical discipline

Learning from others does not require me to agree with everything they say. It requires me to remain curious long enough to understand why they see the situation differently.

I can ask:

• What does this person notice that I do not?
  

• What experience are they bringing to the conversation?
  

• Which of my assumptions are they challenging?
  

• What can I take from this, even if I reject their conclusion?

Those questions turn ordinary conversations into useful ones.

They also change how I lead. Instead of entering every discussion ready to provide the answer, I can enter looking for information I do not yet have. That creates room for people to contribute without first proving that they are the recognised expert.

I have never met anyone who knows everything. I have also never met anyone who knows nothing.

If I listen carefully, every conversation can leave me with a better question, a clearer explanation or a different way of seeing the problem. Copilot can help me capture and revisit those moments, but curiosity is what makes them matter.

The smartest person in the room may simply be the one still prepared to learn.