Implementation Manager

The ability to diagnose a delay without blaming the customer, the product or sales wholesale. Bonus: the candidate names an early signal they could have caught sooner (a late data delivery from the customer, unclear stakeholder responsibility, an overlooked technical dependency). Candidates who have never delayed an implementation are not telling the truth or have not carried a substantial portfolio.

The ability to map stakeholders (executive sponsor, the functional project lead on the customer side, the IT lead, daily users) and to hold a consistent project cadence over weeks or months. Concrete on duration, milestones and escalation moments. Candidates who handle a complex implementation in 2 sentences actually waved standard setups through and did no real implementation management.

The ability to deliver an uncomfortable message without damaging the relationship and without prematurely conceding commercially. Maturity toward the relationship cost of guiding a customer to scope discipline. Candidates who have never contradicted a customer show an overly accommodating service posture that shows up in scope creep, delays and post-go-live frustration.

Prioritization: (1) a clear written escalation to the functional project lead with a documented impact on the go-live date, (2) checking parallel paths (a partial go-live with reduced scope, a 2- to 3-week postponement, an internal workaround for the missing data), (3) communication to the internal sales team and product if the delay has consequences for other customers. Bad sign: the candidate proposes to absorb the delay quietly and let the team compensate for it.

A combination of reading the data (project status, open risks, milestone attainment, ticket history) plus prioritized 1:1s with the 3 riskiest projects plus reading the predecessor's notes. Candidates who jump straight to a generic introduction email to all customers skip the diagnosis and lose trust from day one. Bonus: the candidate names the risk of handover and plans a joint handover meeting per customer with the previous contact.

The ability to hold a position against a sales team pushing for fast conflict resolution. Diagnosis first: why is the project really delayed? Plan: a joint clarification session with the functional project lead and the customer's executive sponsor before commercial concessions are made. Candidates who accept the discount to avoid conflict show a weakness that translates into structural erosion of implementation margins.

Decomposition: (1) standardizing the initial discovery phase (templates, a pre-read questionnaire), (2) reducing the handover gaps between sales and implementation (a joint kickoff, a clearly defined responsibility matrix), (3) structured onboarding phases with measurable exit criteria, (4) self-service components for recurring technical steps. Realistic magnitude: 14 weeks to 8 weeks in 12 months is ambitious; without structural standardization it fails. Candidates who only talk about working faster miss the lever math.

Explicit segmentation by risk and complexity: the 2 riskiest projects (usually the largest contract values or the most critical go-live dates) on a daily or two-day touch, medium projects on a weekly touch with a structured status update, simple standard setups on a two-week touch with self-service components. Bonus: the candidate adjusts by risk signal (a simple project with a late data delivery temporarily moves up). Bad sign: identical touch for all projects, or prioritization by contract-date alphabet.

Diagnosis first: why is the sponsor withdrawing, why low adoption? Weak initial needs clarification, missing internal change management on the customer side, a product that does not fit the actual workflow, or an escalated conflict dynamic. A sequenced plan: (1) a bilateral conversation with the sponsor to understand the real risk, (2) a joint workshop with the 3 most resistant end users to identify friction points, (3) a concrete 30-day action plan with measurable milestones and a clear escalation trigger. Candidates who propose a general re-training session for all end users show a reflexive rather than diagnostic posture.

A healthy cadence: project traffic lights (status per running implementation as red, amber, green) daily on at-risk accounts, milestone attainment and time-to-value per phase weekly, aggregate time-to-value, average project duration and post-onboarding CSAT monthly. Distinguishing leading indicators (data-delivery status, stakeholder engagement, milestone slip) from lagging indicators (a missed go-live date, a post-go-live escalation). Candidates who only look at contract closing or NPS miss the operational steering level.

A typical structure: 75-90 min, opening with confirmation of the customer's business goals (15 min, to be validated by the sponsor), presentation of the implementation plan (phases, milestones, responsibilities) (20 min), clarification of the expected data deliveries and integration points with the IT lead (20 min), communication cadence and escalation paths (10 min), commitments and next steps (15 min). The presence of the executive sponsor on the customer side is mandatory, otherwise postpone. Candidates who describe a kickoff as a product demo or start straight with the technical configuration miss the point of the exercise.

A systemic method: documented implementation phases (milestones at T+1 week, T+4 weeks, T+8 weeks depending on the standard model), measurable exit criteria from each phase (validated data migration, an established champion on the customer side, signed-off configuration), handover standards with the sales lead. An understanding that a consistent implementation cadence is the output of a cross-functional mechanic, not an isolated Implementation-Manager process. Candidates who jump to introducing more templates without changing the underlying sales-to-implementation handover fail.

Openness: the ability to separate the feedback from a personal judgment. Bonus: the candidate names a concrete example of changing behavior after uncomfortable feedback. Candidates who describe explaining their own logic to the manager instead of listening are worth weighting carefully (it can indicate a coachability weakness; the profession requires a lot of self-correction).

A partnership posture: a documented handover with sales (sales context, promises made, identified stakeholders, agreed scope), structured bidirectional feedback; a relationship with the PM as co-construction (structured feedback of needs with business context, not a mere demand ticket out of the running project). Candidates who speak with frustration about product (they never deliver on time) or with condescension about sales (they over-promise) show a teamwork weakness that manifests in operational silos.

Operational maturity: the ability to argue for a postponement when the implementation is not ready, instead of forcing a fragile go-live that explodes in post-go-live escalations. Concrete: the candidate names the project, the pressure moment, the decision made and the actual outcome. Candidates who have never decided against go-live pressure show a bias toward short-term conformity that causes problems for structural implementation quality.