Why performance management systems matter after acquisition

Mergers and acquisitions (M&A) in commercial-property tech aren’t just about balance sheets. They’re cultural and operational puzzles, especially for mid-level software engineers who build tools used by architects and property managers from Dublin to London. Performance management systems (PMS) become the backbone to unify engineering teams, streamline workflows, and keep projects on track amidst evolving objectives.

But what does a practical PMS look like after acquisition? What actually drives better code, smoother integrations, and team morale — versus the theory that sounds nice but falls flat? I've implemented these systems across three architecture-tech firms in the UK and Ireland post-M&A. Here’s what you need to know.

1. Combine KPIs that matter — not just what’s easy to measure

Post-acquisition, leadership loves dashboards. But beware of how vanity metrics creep in. Lines of code or tickets closed don’t reflect real software quality or collaboration in CAD and BIM applications.

At my last acquisition, the acquiring firm initially pushed velocity and bug counts. After six months, the teams switched to KPIs tied to uptime of property management APIs and feature adoption by architect users. The change improved focus on outcomes over output.

Example: One engineering squad reduced API downtime from 2.5% to 0.5% in eight months by tracking service reliability instead of just sprint velocity.

Pro tip: Align metrics with customer-impacting features and legacy system stability, not just engineering activity.

2. Use feedback tools with pulse surveys for culture alignment

Culture clashes are the silent productivity killers after acquisitions. Traditional annual reviews are too slow to catch frustrations brewing across London and Belfast offices.

We introduced Zigpoll alongside Slack integrations for monthly anonymous pulse surveys, focusing on psychological safety, clarity on goals, and collaboration hurdles. Survey responses highlighted cross-team blockers early, enabling targeted interventions.

Data point: A 2023 TechUK report found companies using monthly pulse surveys had 30% higher employee engagement post-M&A than those relying solely on yearly reviews.

Caveat: If overused, survey fatigue sets in. Keep questions short and action-focused or risk disengagement.

3. Standardise performance review templates but customise based on legacy systems

Integrating teams means wrestling with different performance review processes. One company insisted on a rigid quarterly review template; another was purely narrative-based.

The best middle ground? Build a unified template that mandates core competencies — such as code quality, system integration skills, and architecture knowledge — but allows teams to add legacy-specific criteria. For example, the Dublin team tracks integration with their bespoke BIM platform, while the London team adds metrics on CAD plugin stability.

This hybrid approach cuts confusion and preserves domain-specific expertise critical to architecture workflows.

4. Establish cross-site peer reviews to break silos

Post-M&A, it’s easy for Belfast, London, and Dublin teams to retreat into silos, especially given their distinct project focuses (e.g., commercial skyscraper tools vs. historic building renovations).

We set up bi-weekly cross-site code reviews via video calls where engineers critique each other’s modules. This not only raises code standards but surfaces cultural nuances and shared goals.

Result: One team improved defect detection by 20% within four months due to diverse perspectives catching edge cases in property valuation algorithms.

5. Prioritize integrating tech stacks but beware “one size fits all”

Consolidating tools is a must — Jira, GitHub, CI/CD pipelines — but forcing everyone onto a single tech stack can backfire.

In one case, imposing a monolithic Bamboo CI pipeline on the acquired firm caused delays because their microservices-based architecture required more flexible tooling. After a rollback to a hybrid approach, deployment speed rebounded by 35%.

Focus on interoperability and common standards (APIs, code formatting) rather than identical systems.

6. Define “done” collaboratively to align teams and clients

Architectural software projects often involve staged handoffs to property developers, planners, and maintenance teams. Post-acquisition, teams had differing views on when a feature or bug fix was “done.”

We ran workshops including engineers, product owners, and client reps to standardize definitions — from code complete to client acceptance. This reduced rework by 25% over six months by setting clear expectations.

7. Incentivise quality over speed with recognition programmes

M&A often pressures teams to merge velocity goals, leading to rushed deliveries and tech debt. One engineering manager launched a “Quality Champion” monthly award highlighting engineers who improved unit test coverage or reduced support tickets.

This shift encouraged craftsmanship. Unit test coverage across teams rose from 62% to 81% in the year that followed.

8. Incorporate architecture-specific training into PMS

Software engineers in commercial-property tech need ongoing training on industry standards — for example, evolving BIM protocols or UK building regulations that impact software modules.

Link performance goals with completed training modules. An example: after acquisition, all engineers completed a course on the latest ISO 19650 BIM standards. Teams that did ranked 15% higher on code review scores related to BIM integration.

9. Manage remote and distributed teams with flexible check-ins

Post-M&A, many teams split between office hubs (e.g., Dublin’s Docklands and London’s Shoreditch) and remote workers across the UK and Ireland. Standard daily standups often failed due to timezone mismatches.

Switching to asynchronous updates via Jira comments and weekly one-on-ones with rotation worked better. It respects engineer focus time and suits the architecture industry’s project rhythms.

10. Use retention metrics tied to performance insights

M&A periods are prime time for attrition, especially for mid-level engineers feeling lost in new hierarchies.

Track correlation between performance reviews and retention monthly. We noticed engineers whose feedback scores dropped below 3.5/5 had 40% higher churn risk. Early coaching and career-planning conversations helped reduce turnover by 18% in the following year.

11. Plan for phased rollout to avoid “all-at-once” burnout

New PMS implementations sometimes trigger resistance or overwhelm. Rolling out new systems simultaneously across all acquired teams caused confusion.

Instead, we piloted in one office (Dublin) for three months, iterated based on feedback, then rolled out to London and Belfast. This incremental approach improved adoption rates by 60%.

12. Tailor communication styles to engineer preferences post-acquisition

Some teams prefer data-driven dashboards; others want narrative feedback or direct manager conversations. For example, Belfast engineers favoured detailed Jira analytics, while London teams valued Slack-based recognition and peer shout-outs.

Mix communication channels to suit audience preferences. We created a “Performance Management Handbook” summarizing tools, expectations, and communication norms tailored per location.

What to prioritise when your engineering teams merge

Start with metrics that reflect real product impact (uptime, feature adoption). Layer in culture feedback tools like Zigpoll to catch unseen tensions fast. Standardise core PMS elements but preserve specialist architecture knowledge.

Make cross-site reviews and training about shared industry standards your norm. Resist forcing tech stack uniformity if it impedes productivity. Focus on retention signals combined with performance to keep talent engaged through change.

Remember, post-acquisition PMS is about people and processes as much as tools. Get those right, and your teams building the next generation of commercial-property software will thrive.