Hey, Hey P2P'ers! 👋🏾 Remember my Boss Move post about the plugin portal? Here's what happened next. ~~~ 🏆 WIN #1: My report reached Anthropic 4 ways ✅ Email to Anthropic's directory team ✅ LinkedIn note to Cat Wu, Head of Product for Claude Code ✅ LinkedIn note to Boris Cherny, who created Claude Code ✅ A public GitHub issue on Anthropic's official plugin repo, with before and after screenshots Nobody has answered yet. But it's documented, public, and in front of the right people. 🏆 WIN #2: My #1 Reddit post of all time I asked other plugin builders how long their review took. 👉🏾 798 views in about 22 minutes 👉🏾 #74 post on r/ClaudeAI that day Then the moderators removed it because my account is new. 😂 Still, 798 views told me something: other builders want to know too. ~~~ 🔍 THE PATTERN: A VISIBILITY GAP My whole approach comes down to one question: "How will it know?" This time the question was: how will the builder know it's their turn? The portal showed "In review" in two different situations: 1️⃣ Waiting on ME to click Publish 2️⃣ Waiting on Anthropic's reviewer Same label. Different owner. No signal when the handoff happened. ~~~ ⚠️ WHAT THAT COSTS THE PEOPLE USING IT 👉🏾 Lost time: I waited 16 hours on something that was waiting on me 👉🏾 Delayed launches: a plugin can't help anyone while it sits in the wrong queue 👉🏾 Self-doubt: new builders assume THEY did something wrong 👉🏾 Extra support load: confused people send emails and tickets instead of building 👉🏾 Lost trust: when a status can't be believed, people stop believing statuses And it's the same pattern I see everywhere: Water outages. Air quality. Claims. App stores. When people can't see who acts next, things stall quietly. That's why PPCD ends with VERIFIED DONE. ✔️ A status message isn't proof. ~~~ 👀 YOUR TURN Where have you seen a status that didn't tell you whose move it was? "Pending." "Processing." "In review." 😅 Drop it below. Let's train our eyes to spot it. Are y'all with me? 👀

Y’all, I’ve been thinking about how we can make learning together even more useful. I’m going to start sharing short visuals from my own building process, one idea at a time. What would you like to see first: how I spot a problem, how I shape the idea, or how I use PPCD to build it? 👀

And I have to tell you what happened, blow by blow! 🤣🤣 Remember yesterday when I told you I submitted my very first plugin, PPCD Method, to Anthropic’s Plugin Directory? Well, BABY! What happened next turned into a whole UX investigation! 😂 ACT 1: THE WAITING GAME 🤦🏽‍♀️ October 24. I submitted my plugin. ✅ Submission complete ✅ Security scan passed 🔵 Status: In Review I’m thinking, alright Anthropic, do your thing! For the next 16 hours, I’m refreshing my screen, checking my email, waiting for that beautiful “You’re Live!” notification. NOTHING! 🤣 ACT 2: WAIT AH MINUTE! 🤔 Today, October 25, I’m talking to Kevin (ChatGPT), and he asks me one simple question: “Did you click Publish?” Me: NO! Why would I? The screen says IN REVIEW! Y’all, I SAW that Publish button yesterday. I deliberately didn’t touch it because I thought Anthropic was already reviewing my plugin! Kevin tells me to click it. BOOM! 💥 The screen changes to “Publish requested. Your request is waiting for an Anthropic reviewer.” But guess what? The progress indicator STILL says “In Review!” Same status. Two different workflow states! Now my UX brain wakes ALL the way up! 👀 ACT 3: THE PATTERN INSIDE THE PATTERN 🔍 Here’s where it gets interesting. PPCD stands for: Purpose → Place → Click → Verified Done It’s a method I created to help people and AI work through tasks one step at a time, verifying that each action actually achieved its intended outcome. And here I am, experiencing the EXACT problem my method was designed to prevent! 🤣 The system told me where I was, but didn’t clearly tell me what I still needed to do. ACT 4: THE BOSS MOVE 🔥 Now, I could have laughed it off and moved on. NOPE! I had two screenshots, taken on two different days, showing the confusing workflow. So I put on my UX Lead hat. I documented the problem, explained why it happened, and proposed three improvements: 1️⃣ Make required actions unmistakable. 2️⃣ Separate “Awaiting Publish” from “Under Review.”

Hi everyone! Sometimes the next move isn’t adding another feature. It’s showing someone what you’ve already built. I’m reminding myself to stop polishing long enough to let a real person see it. That’s where the useful feedback starts. What’s one thing you could show someone this week? Are y’all with me? 🙌🏾

Hey, Hey P2P’ers! 👋🏾 I learned something from my latest competition. Checking every rule does not guarantee people understand your app. I kept asking: “Am I meeting the criteria?” I checked the boxes. But I also needed to ask: “Will a judge understand the value in seconds?” ~~~ Here’s the clarity gate I’m adding: 1. What does the competition ask for? 2. Where can the judge see proof that I met it? 3. Can somebody with no backstory tell me what the app does, who it helps, and why it matters? 4. Can I explain it clearly in one minute? ~~~ My example: DeHub helps a community coordinator get a neighborhood ready to use WST. WST gathers household reports about water interruptions. For the MITx Global Challenge, I plan to present them together as one coordinated approach. They aren’t technically connected yet, so I’ll be clear about what each one does. ~~~ Try this with your app 👀 Show somebody your opening screen. Ask them what they think it does. If they don’t get it right away, that’s not a fail. That’s your next clue. Are y’all with me? 👀