<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[TrailheadBex]]></title><description><![CDATA[Systems thinker, meaning maker, regenerative leader]]></description><link>https://www.trailheadbex.com/blog</link><generator>RSS for Node</generator><lastBuildDate>Thu, 11 Jun 2026 08:30:08 GMT</lastBuildDate><atom:link href="https://www.trailheadbex.com/blog-feed.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[Scoping Beyond the Brief]]></title><description><![CDATA[How planning a refresh of a portable garden cart at Lake Roland park became a lesson in systems thinking]]></description><link>https://www.trailheadbex.com/post/scoping-beyond-the-brief</link><guid isPermaLink="false">6a1db9c174254bcae084c909</guid><pubDate>Mon, 01 Jun 2026 17:03:33 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/b967e6_8b0b32ad1a8e40d388ff0b8256b9d231~mv2.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>Rebecca Abernathy</dc:creator></item><item><title><![CDATA[The artifact isn't the deliverable]]></title><description><![CDATA[What the Rally Report taught me about why Product Operations work either justifies itself or doesn't. There's a persistent critique of Product Operations as a discipline: that it creates process where none is needed, produces artifacts nobody asked for, and inserts a layer of overhead that good product teams shouldn't require. The critique has some merit. I've seen it play out. Process for its own sake is real, and it's wasteful. But I've also seen what happens when the critique becomes an...]]></description><link>https://www.trailheadbex.com/post/the-artifact-isn-t-the-deliverable</link><guid isPermaLink="false">69fb96e97c50fb68b37edd7f</guid><pubDate>Wed, 06 May 2026 19:55:03 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/d25f00e891ee4dfd96988c984fb72dfa.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>Rebecca Abernathy</dc:creator></item><item><title><![CDATA[What transparency actually gives people]]></title><description><![CDATA[It's not about telling everyone everything. It's about what happens when people can finally see where they fit. For too much of my career, I worked with leaders who operated on a strict need-to-know basis. The message that came down was some version of: "Leadership wants x. I'm not sure why. Can you just figure out a way to do it?" I may have understood the task, but I had no idea what I was actually solving for. And without that, I couldn't bring anything to the table beyond compliance. What...]]></description><link>https://www.trailheadbex.com/post/what-transparency-actually-gives-people</link><guid isPermaLink="false">69f7e2596d919e5ce86bbcb8</guid><pubDate>Mon, 04 May 2026 00:04:53 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/11062b_b7bfaa0850254550b3c23c2ccc4a28f9~mv2.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>Rebecca Abernathy</dc:creator></item><item><title><![CDATA[What I learned from measuring team health instead of productivity]]></title><description><![CDATA[Productivity tells you what a team produces. Health tells you whether they can keep producing. These are not the same thing — and only one of them predicts burnout before it happens. When I built my first team of technical communicators, I set myself a goal that wasn't in any management handbook I'd read: I wanted to know if my team was okay. Not performing — okay. The problem was that most team health metrics I found were really productivity metrics in disguise. Some quantity of output over...]]></description><link>https://www.trailheadbex.com/post/what-i-learned-from-measuring-team-health-instead-of-productivity</link><guid isPermaLink="false">69f7e0f16d919e5ce86bba0c</guid><pubDate>Mon, 04 May 2026 00:01:55 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/b967e6_2e69f114d9fb45b7a4dca4207fcc550d~mv2.png/v1/fit/w_1000,h_576,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>Rebecca Abernathy</dc:creator></item></channel></rss>