New Engineering Leader? Here's How to Assess Your Team Without Six Months of Guesswork

The First 90 Days Problem

You've just taken over a new engineering team. Maybe you're a new VP of Engineering, a CTO joining a startup, or a fractional CTO starting a new engagement. The team is watching. Stakeholders want quick wins. You need to understand: How fast are we shipping? Where are the bottlenecks? Is the team healthy or burning out? Where's the technical debt hiding? What's the bus factor on critical systems?

Traditionally, you'd spend weeks in one-on-ones, reading code, sitting in on standups. By month three, you might have a picture. By then, you've already made decisions based on incomplete data.

What to Assess: Delivery and Flow

Cycle time from commit to production reveals whether bottlenecks are in development, review, testing, or deployment. Interrupt-to-planned work ratio shows how much capacity is lost to firefighting. Definition of Done standards show whether "finished" means tested, documented, and monitored — or just "it compiles."

What to Assess: Technical Health

The "scale 10x" question: where would the system break first? Bus factor: how many critical systems depend on one person's knowledge? Technical debt ratio: what percentage of sprint capacity goes to maintenance vs. new features? These are the questions that reveal whether you're building on solid foundations or a house of cards.

What to Assess: AI Integration

Are AI coding assistants producing a measurable lift or creating more low-quality code that needs fixing? How long does it take a new hire to make their first commit? (This tests documentation and onboarding quality.) Are teams governing AI tool usage or is it shadow AI?

What to Assess: Team Dynamics

Who are the invisible high-performers doing glue work (code reviews, mentoring, documentation) that doesn't show up in Jira? How does the team handle failure — blameless post-mortems or finger-pointing? What's the one thing stopping people from doing their best work?

Practice Scoring: The 90-Day Shortcut

Instead of spending three months gathering anecdotal evidence, run a Foundation Scan. In minutes, you get an objective baseline across all 50 SDLC protocols and 6 delivery phases. You can see immediately: which phases are strong (maybe deployment is solid), which are weak (maybe testing is at maturity level 1), where practices are inconsistent across teams, and what the overall maturity looks like.

This doesn't replace one-on-ones and relationship building. But it gives you an evidence-based starting point instead of gut feel. Your first team meeting can be data-informed from day one.

Building Your Improvement Roadmap

With practice data as your baseline, you can set measurable improvement targets. "Let's move testing maturity from 2.1 to 3.0 this quarter." "Let's get incident response documented by end of month." "Let's reduce bus factor on the payments service." The team can see progress. You can demonstrate quick wins to stakeholders. And six months in, you have trend data showing improvement — not just assertions.