Christian Gloddy

NEW: Internal Threads Internal threads allow you to spin up conversations in Slack from Pylon. It's great when you want to start a conversation with someone, but they primarily use Slack (e.g. engineers, product people or anyone who isn't living out of the support system). Common internal threads we are creating at Pylon: 1/ #bugs to report a potential bug 2/ #project channels to ask a team a question about a specific feature 3/ #feedback to report product feedback to the team It's been one of the most game-changing features we've released and we're so excited to share it with everyone. Enjoy!

44

3 Comments

It'll never be this obvious, but when you're cooking without expert design, you and your engineers will end up JUST LIKE THIS. It's more subtle these days: Missed sprints Unforeseen edge cases Confused customers Broken promises Refund requests Bandaids everywhere Alarming churn Feature bloat Rabbit holing "Nobody gets it, maybe we need an onboarding tutorial!?" ^^ Don't end up in "Panic Land." Get design help now and get it from folks who have been shipping products and building businesses for over 2 decades. #productdesign #apps #SaaS #startupdesign #startups #UX #UI #Productmanagement

11

4 Comments

🙏 Massive thank you to Kelley Poturalski, Nick Mayernik, Evan Lovely, and Andrew Rohman for a great discussion yesterday about what "design-to-code" means and how to approach the challenges product teams face around design systems, collaboration, upskilling, and preparing for the next wave of AI. 🤖 If you missed the live panel discussion, you can catch up with the conversation by watching the recording. Check it out and let us know your thoughts! 💡 https://lnkd.in/gnHSNS3J

7

From Product Talk: Product in Practice: Shifting from a Feature Factory to Continuous Discovery at Doodle Leading a product team (or several teams) comes with its own set of challenges that can be similar to but distinct from the hurdles individual product contributors face. I sat down with Stephanie Leue, Chief Product Officer at Doodle, to dig in to her approach to product leadership, including how she prioritizes discovery and fosters collaboration both inside product and with other disciplines. Read more: https://buff.ly/3Wvdeae ❓ What are some effective strategies your team has used to shift from a feature factory mindset to a continuous discovery approach? How did you overcome any initial resistance or challenges during this transition? #prodmgmt #ux #engineering

1

TestFit Generative Design gives you thousands of buildable outcomes in just a matter of seconds. Input your goals to narrow down you options and optimize the site for your specific needs. Learn more: https://hubs.ly/Q02YQ87v0

37

What do we mean when we talk about "continuous performance monitoring"? It's all about creating guardrails to prevent #webperf / #ux regressions: 🟡 Performance budgets 🟡 Automated testing 🟡 Detailed diagnostics 🟡 Annotated test history Learn more: https://lnkd.in/gDX_9Zuf #pagespeed #sitespeed #webperformance

10

How do you keep engineering teams aligned with business goals while embracing innovation? Ada, the world’s leading customer service automation company, found the answer with Jellyfish. When pivoting to a generative-first strategy, Ada faced a key challenge: balancing innovation with supporting existing customers. They needed clarity on how their teams worked and invested their time. With Jellyfish, they achieved: 🚀 A 14% improvement in cycle times 🎯 Ranked in the top 97th percentile for “days with commits” 📈 Over 10% growth in technical investments “Jellyfish has become our go-to dashboard to understand how we’re operating as a team at a glance,” says William Mora, Head of Engineering at Ada. Now, Ada’s team is striking the perfect balance—focusing on reliability, experimentation, and investments that drive their business forward. Read the full story. Link in comments👇

26

5 Comments

Few agencies without a technical lead are able to get by (and none thrive). Relying on contractors can be a double-edged sword: they bring specialized skills but often lack a cohesive vision that aligns technology with your customer’s long-term goals. This disconnect results in software bloat, where unnecessary features and technical debt pile up. The pain is real: without a consistent, forward-thinking approach, your business is at risk of compounding technical debt that will stifle innovation. Don’t let short-term fixes lead to long-term problems. It’s time to rethink how you approach technology, ensuring it supports—not stifles—your growth.

15

2 Comments

Had a chat with Eric Meyer and Brian Kardell about CSS masonry, does it belong in the grid spec or not? With a bit of a discussion about how and why we ask for developer feedback on CSS. https://lnkd.in/d3C-_dwq #css

33

📟 If you've ever tried to schedule an override with your existing paging provider, you'll know the experience sucks... You try to create an override, end up scheduling the wrong times, the wrong person and end up doing everything twice as a result. We introduced the concept of "Cover Requests" in the launch of incident.io On-call. Rather than setup an override, you tell us when you want cover, and we'll follow up with the other folks on your schedule to get it set up. And now, we've brought that experience to our already delightful-to-use mobile app. So now, you can create that override, or request cover with ease, all whilst you're on the go. Magic ✨

9

Question for engineering leaders (managers, directors, VP's, etc): I'm curious about the current landscape of developer productivity analysis + management tools - things like LinearB and Jellyfish. Which tool, if any, are you using? Any opinions/pros/cons on the tool you're using (or the entire domain overall)?

21

Missed the DevRel Doc Talk? Watch the recording to learn from experts at DevRel.Agency and Fern (YC W23) on how to build developer docs that drive engagement and adoption. Key topics include branding, landing pages, code examples, and CI/CD integration. Watch the full recording 👉  https://lnkd.in/gbN2z_gi #DevRel #DeveloperRelations #DevRelSurvey

8

💡I need your help! 💡 Appeals Doctor is rebranding prior to launching our new self-managed SAAS product and I need help finalizing our logo. I’d really appreciate your input on which design resonates best with you. 👉 Please take a moment to fill out this quick poll: https://lnkd.in/eAUSttQU Your feedback means a lot, and I can’t wait to hear what you think! At Appeals Doctor, we help Amazon sellers manage their account and listing health, saving them both time and money. From unfreezing funds to reinstating accounts and brands, reopening listings, and fixing suppressed listings, we’ve got sellers covered. #AmazonSellers #Branding #LogoDesign #Startups #Ecommerce #FractionalCTO #AppealsDoctor

16

1 Comment

A handy visual guide for Product folks about to contemplate and communicate, well, just about anything. As with so much in our domain, simple at surface, elaborate to execute, but priceless when proper.

16

4 Comments

James Stanier has a good argument for why deadline-driven development is so… difficult → https://lnkd.in/gz3rvj2s “Given that non-technical people don’t understand why software is hard, dates become the stick that they beat you with when you don’t deliver on time. Don’t ask me why, it’s just human behavior. I’m sure you’ve done it when roadworks have taken longer than were specified on the sign, or if a delivery of a package was late. Dates mean something to people, so handle them with care. In fact, perhaps we could do something entirely different instead.” What’s the “something different”? “So, instead, you should take a forecasting approach that follows the uncertainty curve that we outlined above. You start wide, and you taper in. At the beginning of a given project, you might even just have the year that you’re aiming to ship. Then, as you progress, you can start to narrow it down to a quarter, then a month, and finally a specific date.” This is why I will always advocate for time horizon roadmaps → https://lnkd.in/gN8VSYZc

13