
How Pensero turns agentic transformation into measurable decisions
A five-level framework and a measurement cycle that turns AI investment into evidence for the next deployment decision.
Blog
Stories, learnings, and updates from the founders and team behind Pensero.

A five-level framework and a measurement cycle that turns AI investment into evidence for the next deployment decision.

As AI changes how software gets built, the fundamentals of great engineering remain. But how we apply them, the impact we create, and what we expect from engineers are changing.

Why visibility is the safeguard every agentic engineering organization needs.

What working closely with engineering organizations is teaching us about the next layer of AI transformation.

The risks of falling behind, wasting AI budget, and sacrificing software quality as humans and agents share the work.

Why AI-era meritocracy needs better evidence of contribution, with people retaining judgment over rewards and progression.

Why engineering hiring in the AI era needs to look beyond coding skills to judgment, learning, ownership and collaboration.

AI is making it dramatically easier to produce work. The challenge is learning to recognize what is actually valuable.

How AI is lowering the cost of competence while raising the value of judgment.

From AI agent adoption to measurable business impact. How companies should measure the agentic workforce.

Why delivery performance should become part of technical due diligence.

How delivery, quality, rework, and AI leverage can inform board-level choices about hiring, tooling, and engineering investment.

Why successful enterprise deployments start with understanding the customer’s history, workflows and operating model.

The hidden organizational friction behind disappointing AI returns

Technical due diligence often evaluates how technology is described. The harder question is how the organization actually operates.

Why AI model selection is becoming an engineering strategy.

Why the next competitive advantage is understanding AI, not simply using it.

A technical look at linking AI events to people and work artifacts, then evaluating delivery, quality, cost, and team-level impact.

What building Idealista taught me about turning fragmented information into trusted signals for engineering leadership.

Five KPI families for evaluating AI’s effect on delivery, rework, efficiency, cost, and value across teams.

Why engineering visibility feels a lot like finance automation in its early days

The hidden risk of scaling AI without operational visibility

The missing ingredient in AI success: measurement and feedback loops.

Why engineering remains one of the least understood investments in business.

Why measuring efficiency will define which companies survive AI.

What building Google Maps taught me about AI’s potential to become infrastructure and remove real-world friction.

Why engineering visibility becomes critical as companies scale.

How AI changes team structure and leadership decisions, and which signals help evaluate the right mix of human and AI work.

How AI is shifting management from gathering status updates toward judgment, trust, and team development.

Why AI’s economic impact depends on how it changes software delivery, quality and everyday workflows.

The illusion of cheap AI and the rise of uncontrolled usage.

Why measuring performance is essential to understanding complex systems.

How activity-based measurement, disconnected costs, and unchanged workflows obscure AI’s real impact.

Why non-technical leaders struggle to understand engineering teams.

Why rising AI spend needs a performance baseline and a clear connection to delivery, quality, and return.

Why AI-driven capacity growth doesn’t always create value.

What AI-linked layoffs and smaller teams reveal about coordination costs, ownership and the economics of scale.

What my PRs, reviews and collaboration revealed about the work I was forgetting in my self-assessments.

The challenge of linking engineering investment to business outcomes.

Why an AI strategy needs a focused use case, measurable business outcomes and a feedback loop before wider rollout.

How better visibility is transforming engineering conversations in the boardroom.

The hidden gap between perceived alignment and operational reality.

Why engineering performance is harder to measure than other business functions.

Why AI is flooding engineering teams with output, but not always progress.

How accepting AI-generated code without deep review can erode system understanding.

From observation to acceleration. Applying the Hawthorne effect to modern engineering teams.

Engineering cost attribution, work type, and geography in the context of U.S. Sections 174 and 174A.

Why faster AI-generated code needs to be evaluated for regressions and long-term maintainability.

How to turn uncertainty into shared clarity in your first weeks.

Why quick prototypes and business-critical software call for different levels of human oversight when vibe coding.

How AI shifts engineering bottlenecks toward coordination, ownership and faster learning.

If AI changes how work is produced, leaders must change how they observe performance.

The next evolution of leadership: making engineering performance visible.

Pensero’s observations of Cursor, Claude Code, and Copilot adoption, and why usage patterns still need to be linked to engineering impact.

Building engineering metrics that create clarity instead of conflict.

How misaligned metrics quietly undermine high-performing engineering teams.

How team context and individual contribution can inform human judgment without turning AI into surveillance or opaque rankings.

When metrics create uncertainty instead of clarity, trust breaks first.

The system leaders need so promotion, recognition, and performance don’t become political.

How activity proxies, visibility, and missing context bias engineering reviews, with a checklist for spotting misuse.

When boards confuse trust with truth, calibration becomes a dangerous illusion of control.

When engineers can't tell if they're succeeding or failing, your measurement system is the problem

As AI makes code easier to produce, engineering value depends on maintainability, system complexity, and impact over time.

AI doesn't flatten talent. It amplifies it. Here's what separates elite engineers from mediocre ones.

The End of Activity-Based Performance in Software Teams

Why infrequent reviews overvalue memory and visibility, and why fairer conversations need evidence of work over time.

Bridging the gap between engineering reality and executive decision‑making

A three-slide framework for turning engineering trends into a board discussion about risk, strategic bets, and investment decisions.

Why technical, people, and strategy decisions depend on your goals, constraints, and context.

Track leverage, productivity, rework, and learning speed over time to explain whether your engineering organization is improving.

Connect incidents, delivery quality, service health, and operational practices to the reliability risks your board needs to understand.

Use roadmap alignment, work distribution, and initiative progress to show whether engineering effort supports the company’s strategic bets.

A practical approach to self-doubt: record your contributions, set growth goals, and reflect on your progress.

Read delivery flow, AI engagement, rework, developer experience, and focus time together to see where your engineering system helps or hinders the team.

Why AI-assisted coding gains need to be weighed against bugs, rework, and the expertise needed to review them.

Assess talent density, hiring coverage, retention, manager capacity, and onboarding to explain whether the team can support the company’s ambitions.

How lessons from TravelPerk and later engineering leadership roles shaped the tool we wished we had.

A pragmatic approach to AI coding assistants: start with a plan, verify each step and own the code you ship.