Chatter, live agent chat, a 360° view, omnichannel tool, knowledge, Einstein, feedback, notes, reports & dashboards, automations, routing and escalation, user interface, notifications and alerts, self-care (self-service communities and portals), field service lightning,…all these objects and features are essential to reach customer centricity and operational excellence. But how are we supposed to prioritize these epics? What is a good approach/methodology to define the milestones of a Service Cloud implementation project roadmap? As a project lead, budget constraints, technical and business resource availabilities will influence the duration and the scope of a project. An increase in the scope of one project could put pressure on costs and schedules of all other projects. This is why companies should have a strict internal requirements management process that is performance – driven. As suggested in the balanced scorecard model, it’s necessary to have a balanced approached to performance measures that includes customer perception (CxPi, VELO), operational business process efficiency (contact rate, FTR and QRT), Organizational capacity (internal NPS, AHT, cross-selling) and financial performance (growth margin, cost to serve). This scorecard can be complemented by other company-specific KPIs and will serve at least 2 strategic purposes: This model will first help you in monitoring the Service Cloud implementation project in a better way and track if the objectives are met, second the model will help you in prioritizing the epics to define the implementation roadmap.