Care and Lowcode

I attended a webinar this week that didn’t focus on models or architecture, but on geopolitics. Hosted by the Copyright Clearance Center and moderated by Roy Kaufman, the session featured Anu Bradford , known for the concept of the Brussels Effect . The idea is simple, but powerful: The European Union sets regulation that often becomes a global standard. Why this matters beyond a deadline to How do we build above the minimum? We saw it with GDPR . The argument is we’re seeing it again with the EU AI Act . A lot of discussion around the 2 August 2026 obligations focuses on readiness deadlines. What stayed with me from the session was a different framing: The EU AI Act is not a ceiling. It’s a floor. That shifts the question from How do we become compliant?  To How do we build above the minimum? That feels like a very different motivation - one grounded in trust, not just obligation. Why this matters more than a compliance deadline The 2 August 2026 deadline for high-ri...

I don’t have a technical background. And one post about prompting changed everything. On Friday 24 April at 08:30 CEST, I’m presenting at NMTC - the Norwegian Microsoft Technology Community - on:  From Frontline to Low-Code: Building Governed AI Agents Without a Computer Science Degree. This talk comes from a real shift in how I think about AI - and who belongs in it. Register HERE  (I will be presenting in Norwegian) Where this started I spent ten years working in frontline health and social care before I ever touched low-code tools. For a long time, I assumed that meant I was behind - that AI and technology belonged to people who had always worked in those spaces. Then I came across something simple: structure your prompts better. That was the turning point. Not because it was complex - but because it wasn’t. How CGSE came about I didn’t learn prompting from AI. I learned it from social work. Inspired by Microsoft’s GCSE structure, I adapted it into something that made sens...

Cowork has 13 skills. Here is why the architecture matters more than the count. When I first looked at Copilot Cowork, I did what most of us do. I scanned the list. Word. Excel. Email. Research. Familiar tools, repackaged. But that framing does not hold for long. Because Cowork is not designed as one system doing everything. It is designed as a system that decides what to do, when  and shows you as it does it. Cowork helping me prep for my NMTC talk (NO)- Register to join online 24.04.26 (08:30-09:30 CEST   What is actually happening Cowork loads skills on demand. Not all at once. Not invisibly. When it needs something, it activates it. You see it in the interface: Preparing to compose email Loading Deep Research Building a document It is a small detail, but it changes something important. In environments where decisions matter care, public sector, regulated spaces, knowing what is acting is part of trust. Not just the output. The 13 skills (and why t...