At Holden, we deliver projects through our people and our processes.We are a delivery-led, growing business that values clarity, accountability, and practical outcomes. We invest time in getting processes right so our teams can operate with confidence, consistency, and autonomy as the business scales.Our culture is collaborative, and impact-focused. We expect people to take pride in building things that others can use and build on.Roles at Holden suit people who enjoy working closely with teams, care about how work actually gets done, and want to create systems and processes that help people succeed not work around them..Role: Digital Lead plus platform builder1. Role OverviewAs well as maintaining the system into the future, the role will then grow into being the Digital Lead for the company at large. Analysing how we do what we do, staying up to speed with relative digital advances (such as AI), presenting possible digital advances we could make, setting out a Digital Execution Plan, and overseeing its execution.The Platform Builderis responsible for designing, configuring, and maintaining Holden's environment as theSingle Source of Truth (SSOT)for delivery.This role translatesagreed process designs, workflow logic, data structures, and governance standardsinto a coherent and scalable implementation. Using boards, columns, automations, permissions, dashboards, and documentation, the Platform Builder ensures the platform accurately reflects how Holden has agreed to operate.The Platform Builder doesnotdefine business processes or programme scope. Instead, they work closely with process owners and programme leadership to ensure that what is built in faithfully implements agreed ways of working and can scale as the organisation grows.This role is foundational to Holden's ability to scale delivery with confidence, clarity, and control.2. Purpose of the RoleThe Platform Builder exists to:Translate agreed delivery processes into well-structured boards and workflowsEnsure consistent and disciplined use of columns, statuses, automations, and permissionsMaintain the integrity and coherence of the workspace as complexity increasesEnable reliable reporting and visibility through structured, high-quality dataSupport the transition from proof-of-concept builds to scalable, reusable implementationsThis role ensures reflects intended operating models—not ad-hoc workarounds.3. Key Responsibilities3.1 Platform Configuration and BuildDesign and configure boards, groups, items, subitems, and templatesImplement workflow stages using Status, Dropdown, People, Date, Dependency, and Formula columnsConfigure automations for lifecycle transitions, handovers, notifications, approvals, and status changesSet up permissions, board ownership, and access controls in line with governance standardsStructure workspaces to support multi-functional delivery without duplication3.2 Workflow and Data IntegrityEnsure all builds align with agreed process architecture and data modelsEnforce consistent naming conventions, column usage, and board structuresPrevent duplication of boards, columns, and workflow logic across teamsMaintain clear separation between source-of-truth boards and supporting or reporting views3.3 Proof of Concept and IterationBuild and refine proof-of-concept workflows to validate feasibility and design directionTest automations, dependencies, and status logic against real delivery scenariosIncorporate feedback from design reviews and governance forumsProactively identify constraints, limitations, and risks3.4 Collaboration and OversightThe Platform Builder works closely with:Process ownersProgramme leadershipExternal advisorsKey activities include:Participating in design reviews and build walkthroughsClearly surfacing blockers, design gaps, or technical constraintsAvoiding improvised solutions outside agreed design and governance3.5 Platform SustainabilityMaintain clear documentation for boards, templates, automations, and standardsSupport the transition from proof-of-concept builds to scalable, reusable assetsContribute to continuous improvement of the environmentEnsure the platform remains understandable and maintainable by others4. Required Skills and Experience4.1 Platform Expertise (Essential)Hands-on experience building and maintaining environmentsStrong understanding of:Board architecture and hierarchyColumn types and best practicesAutomations and dependenciesPermissions and workspace structureAbility to design clean, scalable templates rather than one-off solutionsExperience configuring dashboards and views for operational visibility4.2 Process and Analytical SkillsAbility to interpret process maps, workflow diagrams, and written designsStrong attention to detail and consistencyComfortable translating abstract requirements into structured buildsSystems-oriented thinking, with an emphasis on data flow and integrity4.3 Ways of WorkingStructured, methodical, and quality-focusedComfortable working within defined governance and standardsClear communicator who raises risks and questions earlyDisciplined about avoiding workaround-driven solutions5. Desirable AttributesExperience supporting rollouts across multiple teams or functionsExposure to:Delivery or programme environmentsOperational reporting and dashboardsOrganisations transitioning away from spreadsheetsExperience working alongside process or transformation consultants6. Success MeasuresThe Platform Builder will be successful if: workflows accurately reflect agreed processesProof-of-concept builds validate the intended design directionBoards and templates are clear, reusable, and easy to understandData quality supports reliable reporting and decision-makingStakeholders trust as the system of record for deliveryHolden can continue platform development independently after Phase 17. Role Context and ReportingWorks closely with Holden programme leadership and process ownersDay-to-day priorities guided by agreed plans and designsCollaborates with external advisors during Phase 1Transitions to internal platform ownership post-Phase 18. Role EvolutionOver time, the Platform Builder may:Take ownership of governance and standardsSupport rollout to additional functions or regionsDevelop more advanced automations and reportingAct as an internal centre of excellence for 9. Experience ProfileThe successful candidate will typically have:3–6 years' experience working with work-management platformsAt least 2 years' hands-on experience building or administering Practical experience configuring:Boards, columns, automations, and permissionsEnd-to-end delivery workflowsExperience supporting operational or delivery teams within governed environmentsDirect experience with is required.The ability to work methodically from agreed designs, collaborate across functions, and maintain platform integrity as complexity increases is essential.