Pluralsight Flow

Pluralsight Flow is a software engineering intelligence tool that gives you everything to help your team build a more efficient workflow. Flow uses data driven engineering analytics to create an insightful foundation to help position your team for collaboration and growth. To learn more about Flow visit us at https://lnkd.in/gJZnGwct #SoftwareEngineeringIntelligence #EngineeringLeadership #EngineeringManagement #SoftwareEngineering

By now, you’ve probably seen the '~9.5% of software engineers do virtually nothing: Ghost Engineers' paper making the rounds. It claims nearly a tenth of engineers contribute nothing and should be fired. Big claim. Bigger miss. Software engineering is collaborative—it’s about solving tough problems as a team. Punitive measures based on narrow metrics do more harm than good, eroding psychological safety and increasing burnout. Metrics are valuable (it’s kinda our gig). But the right metrics empower teams, foster collaboration, and prioritize long-term success over short-term blame. Curious about how to measure team efficiency while keeping team health front and center? Check out our blog—link in the comments.

How do you measure the true impact of the changes you’re making in your engineering organization? Whether it’s testing a new tool, rolling out a process, or adopting Copilot, knowing what’s working (and what isn’t) can be tough. In Flow Like A Pro, we unpack engineering challenges like this and explore how Flow’s tools can help you make sense of the data. In this first episode, join David F., Head of Product at Flow, to see Scenario Builder in action. It’s a simple way to track the before, during, and after of key decisions—so you can tell the full story of your team’s evolution. Let’s rethink how we measure success. ✨💻

We're looking forward to this Thursday—don't miss out! There's still time to register and join us.

1:1s serve many purposes: they’re essential for growth, mentorship, regular check-ins, and understanding where each team member stands. These conversations should foster open communication and collaboration. To support that, we created the Check-in Report in Flow. Check-in provides two powerful views to enhance your 1:1s. With Status Update, you can set goals and quickly assess an engineer’s progress. The Player Card lets you track individual trends across Flow metrics, giving you a more comprehensive view. Together, these tools streamline 1:1s, helping you focus on the discussions that matter most for you and your team member. Learn more about the Check-in Report and how teams at Wolters Kluwer are using it to enable more effective 1:1s for their developers.

We hope to see you there!

By now you've seen that "9.5% of engineers do literally nothing all day" paper making the rounds, claiming that nearly a tenth of software engineers are “ghosts" who contribute nothing to your organization so you should fire them all and save billions of dollars. We have good news: you can ignore it. It's nonsense. Set aside a methodology - "count commits and run them through an LLM pretending to be a committee meeting", basically - that's too ridiculous to even rise to the level of wrong. By the metrics the "Ghost Engineers" paper uses a senior dev who spends their days planning, reviewing code and mentoring juniors has done no work and can be fired at no loss to the company. And that's just senior engineers doing their jobs; management, coordination, leadership, maybe vision? You might think that those things matter, and they do, but they don't exist for this paper at all. Listen: we should all be suspicious of anyone reducing engineering effectiveness down to one number they want to scare us with. Expertise matters, collaboration and leadership matter, nuance and understanding matter. Yes, we should be measuring how our teams are performing; measurement is incredibly powerful as an assistive tool. But if we could buy productivity by the pound, we'd all be doing that already. No metric can replace leadership, and no metric can absolve leaders of their responsibility to understand their organization. We can't let reductive numbers mislead us, and we should definitely never trust anyone trying to scare us with math. We need to put the work in, to truly understand makes our teams thrive. And the only true thing you can say about this Ghost Engineers nonsense is that somebody deeply incurious is going to use it to justify the layoffs that kill their company. We can do–and be–better. Words from Developer Relations Director Mike Hoye

That "Ah-Ha" moment when something clicks is an incredible feeling (I know I loved seeing those when I coached middle schoolers) and engineering leaders can experience the same thing! Listen below to one of our customers describe how they've been surprised and excited when they learn and grow after reviewing data in Pluralsight Flow #EngineeringLeadership #EngineeringMetrics

Building great teams isn’t magic—it’s precision. Carpenters have tape measures. Runners have stopwatches. But when it comes to team performance, many leaders are still winging it. Why? On December 12th, join Mike Hoye, Sage Rozzel, and some of our customers for a webinar that breaks down how Flow turns raw data into actionable insights. Here’s what you’ll take away: 💻 Spot bottlenecks before they slow you down. 💻 Bring your team along the adoption curve for metrics-driven leadership. 💻 Use real-world examples to align your teams and hit your goals on time. This isn’t theory—it’s the playbook for teams who’ve found their Flow and thrived because of it. Ready to ditch the guesswork? Save your spot today! https://lnkd.in/g2VBhT5j

What’s the most effective way you’ve found to celebrate and communicate small wins in your team?