Activity
Mon
Wed
Fri
Sun
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
What is this?
Less
More

Memberships

Clief Notes

40.1k members • Free

The AI Advantage

126.2k members • Free

Strength Therapy

2.3k members • $34/month

18 contributions to Clief Notes
Every team is building context in silos. We're trying to fix that.
I'm working on something I haven't seen discussed much here and genuinely want to know if others are in the same territory. We are trying to solve 2 problems. The first is that every team in our organisation is building AI context in isolation. Same knowledge being captured five different ways, no shared foundation, nothing governed or reusable. We've got enterprise knowledge that technically lives in SharePoint but is effectively invisible to any AI system. We want to fix that by building structured context at two levels: enterprise-wide knowledge that any team can draw on, and domain-specific knowledge owned by each business area — both stored as markdown, governed properly, with SharePoint as the interface for people who don't want to think about files. The second problem is how Technology handles demand from the business. The process for defining requirements, producing the right documentation has always been difficult as business areas often leave it to Technology. The outcome we are trying to achieve would be when a business area raises a need, an AI system — already loaded with the right enterprise and domain context — takes it through a defined process and produces a brief that engineers and their AI coding tools can act on directly. No discovery from scratch every time. The knowledge is in the system, not locked in someone's head or their OneDrive folders. The hard parts are not the AI. They're: - Getting operational detail out of each business domain at the granularity AI can actually reason about - Stopping teams building their own siloed context again the moment you turn your back - Building governance so the system earns autonomy progressively - Getting stakeholders to engage through the system rather than around it We have a later phase in mind where the system proactively surfaces opportunities by monitoring operational data — but we're keeping that parked until the core is stable. We are a small team in the early stages of planning the work.
0 likes • 2h
@Aaron Klein This is really useful, thank you. A lot of what you've described is close to what we've already put down on paper, so it's reassuring to see the same shape turn up somewhere else independently. The one accountable owner rule is already built into how we're designing domain knowledge ownership. Each domain has a named person responsible for accuracy and currency, not a team, and that person has to flag material changes within a set number of days rather than waiting for an annual review. Generated output works the same way you describe it too. A specification the AI produces doesn't count as approved until a human signs off on it, and every version is tracked so we can trace which version of the knowledge produced which output. Your intake queue maps closely to a five-stage pathway we've designed, from mapping the business need through to a structured brief for engineering, with checks built into the stages rather than sitting as a separate review bolted on afterward. And the autonomy point lands exactly where we've landed too. Everything gets human review at the start, and the system only earns less oversight once it has built a track record, not because we decided in advance to trust it. Two things I'd love to know more about: - On the 60 to 90 day buildout for around 180 files, is that mostly getting the structure and schemas standing up, or does it include the actual domain capture work, sitting with subject matter experts and pulling the operational detail out of them? I'm curious about the size of the team and how long it takes once you're deep into a real domain. - And on stopping teams from rebuilding their own silos the moment attention moves elsewhere, was that mostly a governance fix, naming owners and setting obligations, or did making the shared system genuinely easier to use than going it alone do more of the work? We're planning for both, but haven't tested which one actually holds people's behaviour in practice.
ICM in Copilot Cowork? Yep, sorted.
EDIT: the use of copilot-instructions.md is very unreliable. Despite clear instructions to load the ICM workspace and read the setup.md at launch, 9 times out of 10 it fails with no meaningful error. Copilot itself tells me that these instructions are more like suggestions.🤣🤣 Instead I have built a skill in Copilot co-work and I have built an agent for the standard Copilot chat. Both of these will reliably launch into my ICM workspace. -------------------------------------------------------------------------------------------------------------------------------------------------------------- We've gone back and forth, here, on whether ICM can work inside Microsoft Copilot. I can now say it definitely does, and that Copilot Cowork is where it works best. I spent today rebuilding my own ICM workspace, currently in Claude, for Copilot — routing file, room context files, a voice file, branding, shared references — and it maps over almost one-to-one. The folders-and-markdown approach we use is almost exactly how Cowork is built to work. Your files live in OneDrive, Cowork reads them on demand, and you get the same context-on-demand behaviour we're used to. Two things make Cowork good for ICM, particularly in a business environment: - It reads your ICM folder tree straight from OneDrive, so you stop re-explaining yourself each session. - It has native access to Outlook, Teams, calendar and SharePoint, so rooms that interface with those apps or their data get easier - The adjustments were small: Copilot itself rewrote my Claude.md to a Setup.md, native M365 instead of connectors, and tightening the original markdown, which had grown, to keep token use down. NB: Copilot, to me, seems a smidgen slower than Claude (Yes, I have Opus 4.8 enabled in Copilot) Guide and blank template at RockfieldIT/icm-copilot-cowork: Implementing ICM in Microsoft Copilot Cowork
1 like • 15d
Thanks for this - I had it pretty much set up - just needed the one extra copilot-instructions to make it easier to use. thanks
1 like • 14d
@Colm Whelan TBH I don't use copilot a lot because I find Claude so good but I'm going to start exploring more.
Your AI expert council is probably making worse decisions than a single prompt
Everyone's stacking AI experts into "councils" right now. Here's what nobody mentions: most of them produce blander advice than a single good prompt. I've been building multi-agent systems for a while, and the council pattern is seductive. Load six marketing legends, let them debate, synthesize the genius. Three things I learned the hard way: 1. Councils regress to the mean. Put Cialdini, Godin, and Vaynerchuk in a room and "synthesize" their answers and you get generic marketing advice wearing three nametags. The fix isn't a better synthesizer. Stop resolving the disagreement. Let the tension stand and make one agent own the call. 2. The debate is where your budget dies. Distilling a book into a tight skill file is cheap. Having agents argue in real time is not. If "minimal tokens" is your pitch, the preprocessing is doing the work and the roundtable is the luxury. 3. It doesn't make the model smarter. Cold Claude already does a soft version of all of this. What the structure buys you is named, sharp, predictable behavior. Say that honestly — the moment you claim it makes the AI "smarter," you've oversold it. None of this means don't build councils. It means build them with your eyes open. The real test for any council: do your experts actually disagree, or do they just agree in different vocabulary? If it's the second, you built one expert and gave it six hats. (Riffing off the systems thread from @Curtis Hays that @David Vogel highlighted for us and the 'systems' build — good work worth pressure-testing.)
1 like • 20d
I've been using an ai council based on Karpathy's LLM Council Method (found the idea/ resource here statics.teams.cdn.office.net/evergreen-assets/safelinks/2/atp-safelinks.html ) I find it a great way to pick holes in what I'm working on so I can prepare for potential questions I might get from stakeholders/ peers or find gaps in what I'm working on. I'm not really using it to help me make decisions. Has anyone else tried this? I'm also working on adding my executive as an additional advisor.
1 like • 16d
@Gabriel Azoulay thanks for the feedback. I'm finding it a really useful tool. I'll let you know how it goes once I add the executive as a role.
😫 Speaking on camera (pre-recorded) - anyone cracked this?
Live calls, Teams meetings, I'm fine. Looking straight down the lens answering a question, no problem. Trying to record something for my landing page (new biz) and I genuinely cannot do it. Six hours in. Nothing is working. I've tried winging it from bullet points. I've tried a full script with a few teleprompter overlays. Both feel stiff and unnatural the second I hit record. Has anyone actually figured this out? Because it's low key denting my confidence and I know it's something I need to crack 🙏1
1 like • 20d
I think like others have suggested - practicing it over and over. Depending on how professional it needs to be - record it while your out and about so it doesn't feel so forced. Make a commitment to try and recording every day for 30 day - I'm sure you'll see an improvement.
What would you do?
I started 2026 thinking I was going to go to law school. but after looking at the mass amount of debt I would be in I am starting to change my trajectory. I got offered a job implementing tech (specifically AI) into different companies. I would start off with a vending machine business and once I complete that I would move on to law firms with the help of my employer. I am DESPERATE for guidance! where would you guys start? I could see this being a career for myself. if you were in my position as a 23 year old starting from scratch with amazing opportunities, where would you start? I desperately want a mentor! thank you guys!
1 like • 22d
@Kushnir Achi 100% harder - especially when you need the business side to champion the change within their own teams.
0 likes • 20d
@Jordan Shaw yep and often overlooked
1-10 of 18
Peta Vigor
3
31points to level up
@peta-vigor-1240
I'm a Business Transformation Manager and want to improve my AI skills. I'm thinking about how we can use AI strategically within the organisation.

Online now
Joined Mar 27, 2026
Brisbane
Powered by