Andreas Prins

🔥 The automation game just leveled up. Today I spotted something BIG inside ChatGPT: 👉 ChatGPT Business is being rolled out, with connectors to internal sources. This is huge. Why? Because I’ve been playing with something similar lately: ✨ ChatGPT as the UI ✨ n8n as the backend ⚡ Together = automation magic merge And guess what? n8n just launched their AI workflow builder → you can literally vibe code workflows in plain language. Combine that with ChatGPT’s new Business features, and suddenly automation becomes a superpower anyone can adopt. We’re entering a new era where: AI isn’t just answering questions, it’s running your workflows. No-code + AI = infinite leverage. The people who master this NOW will be lightyears ahead. 🚀 ⚡ FOMO alert: if you’re not experimenting with this, you’ll be watching from the sidelines while others automate everything. 👉 Follow me here on LinkedIn for more n8n + vibe coding automation tips. 👉 And check the first comment to subscribe to my YouTube channel where I’m dropping tutorials and real-life workflows. This is only the beginning. The future of work is being rewritten, are you in? 💡 #ChatGPT #n8n #Automation #AI #NoCode #AIWorkflows #Productivity #FutureOfWork #VibeCoding #BusinessAutomation

128

31 commentaren

“Teams saved me from myself. I didn’t even realize that info was on my screen until I got the notification!” Sensitive Content Detection in Teams is now rolling out the Teams Premium users! Have you ever felt that moment of panic when you realize you might be sharing something you shouldn’t in a meeting? With Microsoft Teams’ new sensitive content detection feature, those heart-stopping “oops” moments may soon be a thing of the past. Now generally available as part of Teams Premium, this feature helps detect accidental exposure of sensitive information during screen sharing, helping keep confidential data private, even in cases of unintentional overshare. Let’s look at a few real-world examples of how sensitive content detection can be a game-changer in everyday Teams meetings: Sales & Finance Calls: A sales manager is sharing a proposal spreadsheet with a client over Teams. On another tab of that spreadsheet, there’s a list of customer account numbers and credit card details used for billing. In the past, clicking the wrong tab could expose all that sensitive client info. With content detection on, the instant an actual credit card number appears on screen, Teams will flag it and alert the presenter to hide it. Human Resources or All-Hands Meetings: In a company all-hands, an HR representative shares a slide deck reviewing employee benefits. Unbeknownst to them, one slide has a screenshot that accidentally includes an employee’s personal information. As soon as that slide comes up, Teams will warn the presenter in real time. Note that Teams will send a notification when there's a high level of confidence in the match, avoiding alerts for loose or uncertain pattern matches to minimize unnecessary interruptions. Project Meetings with External Guests: You’re in a project update call with an external partner. You need to show a document from your screen. That document, however, has some placeholder text like “Passport No: 123456789” for a user profile. You forgot to scrub it. Teams’ detection kicks in and spots the passport number on your screen, even though it’s just an example – it doesn’t know it’s fake, and that’s good, because in a real scenario it could have been a real passport number. You get a nudge, quickly stop sharing that part of your screen, and explain you’ll provide the data through a more secure channel. Even the most careful users can make a mistake. By building smart detection into the meeting experience, Teams helps prevent those moments from becoming problems. In summary, the general availability of sensitive content detection in Teams meetings is a milestone that marries security with usability. It’s a guardian angel for your screen shares, stepping forward only when needed. Teams is not just the platform you work on – it’s a partner that’s looking out for you. And as you head into your next presentation, you can feel a little more at ease, knowing that “Teams has my back, no matter what’s on my screen.”

61

1 commentaar

GPT-5 is live in Copilot Studio! Same day as the OpenAI release. Same day as Microsoft 365 Copilot. That’s impressive. But what really matters: we now have GPT-5 in Copilot Studio. That means better reasoning, better orchestration, and a lot more potential for building serious agents. I’m curious to see how far I can push this and if this solves a couple of limitations I had building Agents. The foundation just got a major upgrade, now it’s up to us to build on it. https://lnkd.in/eYetDwk2 #CopilotStudio #GPT5 #PowerPlatform #Copilot #AIBuilder

39

2 commentaren

PMOs don’t fail because of tools. They fail because of silence. Think about it: • A risk raised too late, when it’s already burning. • A sponsor left in the dark until the project derails. • A portfolio report that shows data but hides the real story. And then we wonder why trust is lost. Here’s the truth: A PMO’s biggest problem is not process. It’s relevance. Updates don’t move projects forward. Decisions do. PMOs spend their days in endless meetings collecting updates, recycling the same slides, and they wonder why nobody listens. The truth: Your value isn't in tracking activity. Your value is in keeping work moving and enabling decisions. A PMO that understands cadence, status, prioritisation, and communication becomes strategically valuable. Because it's not about "being busy." It's about creating the right decision at the right time. Here's what changes everything: Ask yourself ❓Are your meetings aligned to decision moments? ❓Does your status page make it obvious what to decide? ❓Can you defend why one project matters more than another? ❓Do you have the language to handle tough sponsor conversations? If not, here’s what I've learned works👇 1️⃣ Cadence That Works - Daily → unblock teams - Weekly → risks & dependencies - Fortnight → steering (decisions only) - Monthly → portfolio review 2️⃣ Status 1-Pager - Translate one status report into a 3-line business impact summary. - RAG + forecast - 3 highlights, 3 risks with owners - 2 decisions with options - Budget & benefits variance 3️⃣ Prioritisation Model - Score projects 1–5: Value, Fit, Urgency, Effort, Risk - Weight criteria based on strategic context - Transparent ranking sparks conversation, reduces politics Note: Politics and dependencies will adjust pure scoring 4️⃣ Communication & Scripts - Keep a “story bank” of real wins and failures to share with leaders. - Map influence vs interest - Message format: headline → so what → action → deadline - Prepare scripts for: scope creep, date pressure, resource gaps 🧩 Pro tip: Cancel any meeting that has no decision on the agenda. You'll gain instant credibility and protect leadership's time. 💼 Practice: Take 3 active projects. Score them with the prioritisation model. Does the ranking match your sponsor's gut feel? If not, you've found a valuable conversation to have. Don't try to tackle all four at once - that's overwhelming for anyone.Choose whichever foundation resonates most and give it a proper try. ______ ✳️ This is part 2 of 3 on mastering PMO In Action. Missed part 1? Check here: https://lnkd.in/dR7-89zm 👉 Save this cheat sheet! 👉 Want the full 15-item PMO Upgrade Guide with templates and scripts? Download it here: https://lnkd.in/dWgE53x2 ______ 👉 Need help on your PMO transformation? I’m Pierpaolo. I help ambitious professionals transform their career using AI applied to PMO and project leadership. Book a call with me: https://lnkd.in/dTNUPQwT

95

30 commentaren

🔐 Happy and secure Monday, Fabricators! A new way to secure your Fabric workspaces has just landed. 💡 Last year in May, the Fabric product team announced GA of tenant-level private links. Last week they introduced (in Public Preview) private links for Fabric workspaces. The feature makes it possible to control private network access per workspace instead of at the tenant level which allows users to apply differentiated controls across business units, dev/test/prod environments, data domains, or projects. ✨ Well, I'm not surprised customers (including regulated ones) shared  feedback asking for more granular network security controls after Microsoft released tenant-level private links. Most enterprise customers have tons of workspaces, often managed by different teams. In my opinion, most if not all administrative settings (including those around security) should be available on different levels of granularity (ideally tenant - domain - workspace?). ❓ In your opinion, what scenarios could benefit from workspace-level private links (if any)? ➡️ Read more: https://lnkd.in/d79zvb7g *The diagram below is from the Fabric documentation. #MicrosoftFabric #security #networking #PrivateLink #administration

40

𝗕𝗿𝗲𝗮𝗱𝗰𝗿𝘂𝗺𝗯𝘀 𝗼𝗻 𝗦𝗵𝗼𝗽𝗶𝗳𝘆: 𝗠𝗼𝗿𝗲 𝗖𝗼𝗺𝗽𝗹𝗲𝘅 𝗧𝗵𝗮𝗻 𝗧𝗵𝗲𝘆 𝗠𝗮𝘆 𝗦𝗲𝗲𝗺 A client asked me recently: “Can we add breadcrumbs so customers can easily get back to where they came from?” Seems simple, right? But here’s the tricky part: how do we know what page a customer came from and more importantly, what should the breadcrumb actually show? 𝗪𝗵𝘆 𝗯𝗿𝗲𝗮𝗱𝗰𝗿𝘂𝗺𝗯𝘀 𝗺𝗮𝘁𝘁𝗲𝗿: 1. Better user experience: they help customers understand where they are and navigate back easily. 2. SEO benefits: Google uses breadcrumb structure to understand your site hierarchy, and even display it in search results. But here’s the catch: not all breadcrumb setups are good for SEO. There’s a browser API called the history API that can technically track a user’s navigation path. But it’s not recommended because it reflects an individual’s session rather than your actual site structure. For search engines, that’s confusing. 𝗦𝗼 𝘄𝗵𝗮𝘁’𝘀 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝘄𝗮𝘆? Breadcrumbs should reflect your store’s hierarchy — not just where the user has been. But on Shopify, this gets complicated: • A product can belong to multiple collections • There’s no such thing as a sub-collection, and • Shopify doesn’t enforce parent-child relationships Shopify's answer to the issue of breadcrumbs was 'collection-aware' URLs. Basically, you can set a 'parent collection' on any product page by adding the collection handle to the URL but this went out of fashion years ago because its typically not a good idea for SEO to have many URLs for a single product page. 𝗧𝗵𝗲 𝗺𝗼𝗱𝗲𝗿𝗻 𝗮𝗻𝘀𝘄𝗲𝗿? 𝗠𝗲𝘁𝗮𝗳𝗶𝗲𝗹𝗱𝘀. One great workaround is using metafields. We can set up a metafield on product or collection pages that defines the breadcrumb path, giving merchants full control. This works well, but the downside is: For large catalogs, it can require a lot of manual input. In other words, it doesn’t scale easily. In one client project, we went a step further: In 2023, Leo and I used metafields to not only link two collections in a hierarchical structure but also created metaobjects to simulate categories and link these to child collections as well. Whatever the solution, there's no one rule to infer what collection makes the most sense for a particular collection or product unless you can maintain a strict one-to-one relationship between collections and products. 𝗧𝗵𝗲 𝗯𝗼𝘁𝘁𝗼𝗺 𝗹𝗶𝗻𝗲: Breadcrumbs seem simple but in Shopify, it's not so intuitive. There’s no one-size-fits-all solution. But with smart use of metafields (and a bit of planning), you can build a structure that improves UX and gets Google on your side. Have you added breadcrumbs to your store? Would love to hear how you approached it.

80

27 commentaren

RECRUITMENT AGENCIES: WHAT'S YOUR POSTURE TOWARD AI? I'm hearing three narratives from my conversations in the agency side of the business. 1️⃣ RADICAL AI ENTHUSIASTS (circa 10%) Some enterprise scale staffing firms are going 'all in' on AI and clearly see that their future is going to look very different from having legions of salespeople making outbound calls. I'm ALSO seeing radical AI enthusiasm amongst staffing firms at the other end of the scale, especially solopreneur businesses, where AI can scale up the punching power of a small business 2️⃣ INTERESTED BUT CAN'T OPERATIONALISE (60%) AI is great but existing modus operandi and urgent, short term deadlines means they can't implement new ways of working behind using a few pilots here and there. AI is in the business, but mostly at the front end and bought via AI-enabled features from existing tools. Needs an AI Operations Lead or external consultancy to support the change 3️⃣ AI SKEPTICS (30%) Business is tough, but old ways continue to make hay. There's definitely a regional vs metropolitan divide here - companies who focus on region, still drive a huge amount of their business from relationships built over a long period of time - old school methods of reviving these relationships still work - even (gasp!) using the phone! WHICH ONE (1️⃣, 2️⃣ or 3️⃣) IS CLOSEST TO YOUR POSITION? In any of these cases, though you should pay attention to Popp. Doing a webinar with these guys tomorrow (no more seats left!) so I'll see you there if you've already signed up; otherwise and also: sign up for LIVE DEMO whilst they walk through options of how to operationalise AI in your staffing business https://lnkd.in/eHeArjfV

36

45 commentaren

🍳 The egg organization So, let’s talk about something we’ve all seen: the “egg organization.” It’s a funny name, but it really paints the picture of what happens in a lot of companies trying to shift to product mode. Here’s the idea: you’ve got your product team (engineering, design, product management) they’re all thinking in terms of building scalable products. That’s the yolk in the middle of the egg. But then you’ve got the rest of the organization (sales, operations, marketing, all the adjacent functions) still operating in project mode. That’s the egg white surrounding the yolk. And that’s where the challenge comes in. Even if your product core is ready to think in product mode, the rest of the organization can pull you back into project thinking. It’s like you’re trying to move forward, but you’re still stuck in the old way of doing things. So, the real question becomes: do we want to fully embrace product mode, or are we okay staying in project mode? And if we want to make that shift, how do we get everyone on board so that the whole organization is aligned? That’s the essence of the egg organization, and it’s something we’ve seen a lot. It’s a reminder that a true shift to product mode is about more than just the product team, it’s about bringing the whole organization along for the ride.

42

12 commentaren