Mary Rogers

Curious: has anyone found a particular sub-agent role or setup that's been especially powerful? Would love to compare notes. I've been experimenting with Claude agent teams lately, and one thing stands out: the software paradigms we've always relied on (API design, test coverage, modularity) matter more when working with AI, not less. Giving each sub-agent a specific role (Team Lead, Frontend Dev, Backend Dev, QA Engineer) produced noticeably better results than asking one agent to do everything. Wrote up what I learned using a calculator app as the example. Link in the comments.

12

1 Comment

I love the idea of giving more autonomy and agency to our non-dev contributors. Product managers are already able to create prototypes with AI. Now, they can go one step further and actually contribute to the codebase. Chatting with GitHub Copilot directly from Teams, or opening a pull request from an issue with Copilot — this is just the beginning 🚀 This will clearly impact our development workflows: 🤏Shorter lead times for small and medium tasks 💨Faster path from idea to production 🚀Fewer handoffs and less friction Of course, developers may feel concerned — maintaining additional code written with AI, even after review, can be uncomfortable. But this is also a great opportunity: 👉 to better document developer expectations 👉 to formalize coding standards, architecture rules, and best practices 👉 so the AI can follow those guidelines and produce compliant, maintainable code Empowering PMs doesn’t mean replacing developers. It means raising the bar for collaboration between humans and AI — and between product and engineering. Curious to see how this evolves 👀

3

Why neutrality in #SoftFurnishings is harder than boldness (And why I’ll always choose it.) 1️⃣ Neutral isn’t minimal. People often confuse neutral palettes with playing safe. But designing a neutral space that feels complete takes far more restraint than going bold. It’s easy to fill a room with colours and patterns. Much harder to know when to stop. 2️⃣ It takes discipline to edit. When clients see an empty corner, their first instinct is: “Let’s add something.” My job is to pause, feel the energy, and ask, “Does the space need more? Or are we avoiding stillness?” #HealingSpaces often breathe through the things we remove. 3️⃣ Quiet choices hold deeper power. A soft textured rug or a muted sheer aren’t background details. They are anchors. They guide the way you feel, move, and think. 4️⃣ Neutrality requires deep listening. Not just to the client, but also to the space. The walls. The light. The emotional weight of what already exists. If you listen carefully, you’ll often realise: The space always says something. You just need to honour it. 5️⃣ Bold is easy, but balance is tricky. Using statement colours is easy.  It takes a calibrated mind to design a space that feels peaceful and subtle. That is what makes neutral spaces feel timeless. Not boring, but deeply human. 💬 Have you ever walked into a room and felt instantly calm, without knowing why? *********** 🏡 Follow Darsha Manek for more on Soft Furnishings. *********** #LuxuryDesign #Entrepreneurship #EnergeticAlignment #Fabrics #Trends #HealingSpaces #SoftFurnishing

13

Having to cut scope is just a fact of life for a PM or designer. There are often these little surprise-and-delight features that you want to build because they would just be *cool*, but the reality of timelines and constrained engineering resources force you to have to say no (often to yourself 😅). Ok you can guess what I'm about to say... Yeah, AI can solve that. Below is a demo from Justin Truong, a Senior Brand Designer at Intercom. Justin was working on the new site for Pioneer, our annual event for AI CS leaders. He had a really cool idea to bring the Pioneer brand to life, adding interactions to make things feel like pollen flowing through air (you know, like pollinating ideas 🤯). But he faced constrained engineering capacity. So he turned to Claude. Within 3 hours, Justin was armed with code that's now live on the site. Could we have lived without this? Yeah. But is it really cool? Does it add just that little something extra to uplift the site, the Pioneer brand, and make everyone's experience of it just that more delightful? Definitely. It's often those those small details that can make all the difference in your customer experience. Now, anyone can make them happen. Learn more about Pioneer and experience Justin's idea yourself at the link in comments 🌼

16

1 Comment

🤖 I love how the discipline of doing things right rarely gets appreciated - until it unlocks possibilities you didn't even know existed... Check out how I can now ask Claude about our team performance 👇 We've been tracking engineering metrics at loveholidays since day one - from team health and code quality to performance data, even building them into data products. It was an investment to ensure our environment and culture was as great to work in as it was performant. Recently, thanks to this investment and the brilliant work of Stuart Caborn, Misha Griffiths and George Malamidis, we were able to connect our data to Claude via MCP. Meaning we can now have conversations to explore six years of performance insights. We've all heard that engagement drives performance, but here is what our data actually shows: Teams with high health scores show: → 40% faster code reviews → 25% higher goal completion → 50% fewer escalated incidents It's a reminder that new technologies don't create value out of nothing. They amplify what you've already built. The invisible work we did for years - tracking data religiously, making it accessible, having organisational patience - that's what made this breakthrough possible. What foundational work is your organisation undervaluing today? #TechLeadership #EngineeringLeadership #AIIntegration

67

15 Comments

One thing I see a lot in mid-market engineering teams: Senior engineers are slammed. Just not always on the work that moves the product forward. The teams that actually ship the product aren’t always the ones with more people. They’re the ones where senior engineers get to spend their time on the work that matters most. In smaller engineering teams, every senior engineer matters. But a lot of that time goes to operational work. Things like testing cycles, manual reviews and keeping systems running. Important work. It has to happen. But it doesn’t always require your most experienced builders. One developer put it like this during a workflow discussion. “We spend a lot of time keeping the machine running.” The teams that start pulling ahead usually do two things. They automate more of that operational work. And they make sure the right people are handling it. Senior engineers get back to building the product. That’s where mid-market teams gain real leverage.

13

Curious how other companies structure their platform teams when supporting thousands of engineers? I broke down the org design choices I've made, from team size to ownership models to communication patterns. Link to post in comment 👇🏻

15

6 Comments

It seems pretty clear to me that the fastest moving product teams will be those that are obsessed with building systems that review and revise code from agents to be clean, fast, and secure. Put amazing engineers on this task full time. Then give the people who know your product, customers, and space a ton of tokens to create code that goes through that system and comes out shippable product work.

7

1 Comment

💥 I just found a foundational flaw in Claude. All models, all interfaces. Repro steps below: 1. Go to Claude settings 2. Attempt to update your email address 3. If you can’t find how to do it on your own, ask Claude how to change your Claude email address 4. Validate that Claude is not hallucinating by going to https://support.claude.com and searching for “How do I change the email address associated with my account?” 5. Shake your head and think “sorry users, I know we kind of slid past this when you signed up. Hope the email you used to sign up never gets compromised or needs to change – magic links or SSO are the only option (darn it). And if it does, hope you didn’t buy an annual PRO plan because no refunds / transfers even if to the same human ✌ (grrrr…)” Perhaps this behavior is the result of conscious prioritization based on a thorough understanding of needs / trade-offs. If this behavior was an oversight, then based on prior trips on the modernization train, this could be a massive slog of tech debt. Particularly in a hyper-growth business dependent on uninterrupted & high-integrity data access / entitlements / provenance. Product people – let's use this moment to build foresight! - Don’t abdicate PM or UX from “technical” discussions about data models, identity, or access control – decisions within these domains have incredible implications - Customer onboarding & admin workflows are foundational CX, not afterthoughts - If you’re using Claude Code, invest in Git + GitHub integration for improved resilience (and much more)

3