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 builder
1. Role Overview
As 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 Builder
is responsible for designing, configuring, and maintaining Holden's environment as the
Single Source of Truth (SSOT)
for delivery.
This role translates
agreed process designs, workflow logic, data structures, and governance standards
into 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 does
not
define 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 Role
The Platform Builder exists to:
* Translate agreed delivery processes into well-structured boards and workflows
* Ensure consistent and disciplined use of columns, statuses, automations, and permissions
* Maintain the integrity and coherence of the workspace as complexity increases
* Enable reliable reporting and visibility through structured, high-quality data
* Support the transition from proof-of-concept builds to scalable, reusable implementations
This role ensures reflects intended operating models—not ad-hoc workarounds.
3. Key Responsibilities
3.1 Platform Configuration and Build
* Design and configure boards, groups, items, subitems, and templates
* Implement workflow stages using Status, Dropdown, People, Date, Dependency, and Formula columns
* Configure automations for lifecycle transitions, handovers, notifications, approvals, and status changes
* Set up permissions, board ownership, and access controls in line with governance standards
* Structure workspaces to support multi-functional delivery without duplication
3.2 Workflow and Data Integrity
* Ensure all builds align with agreed process architecture and data models
* Enforce consistent naming conventions, column usage, and board structures
* Prevent duplication of boards, columns, and workflow logic across teams
* Maintain clear separation between source-of-truth boards and supporting or reporting views
3.3 Proof of Concept and Iteration
* Build and refine proof-of-concept workflows to validate feasibility and design direction
* Test automations, dependencies, and status logic against real delivery scenarios
* Incorporate feedback from design reviews and governance forums
* Proactively identify constraints, limitations, and risks
3.4 Collaboration and Oversight
The Platform Builder works closely with:
* Process owners
* Programme leadership
* External advisors
Key activities include:
* Participating in design reviews and build walkthroughs
* Clearly surfacing blockers, design gaps, or technical constraints
* Avoiding improvised solutions outside agreed design and governance
3.5 Platform Sustainability
* Maintain clear documentation for boards, templates, automations, and standards
* Support the transition from proof-of-concept builds to scalable, reusable assets
* Contribute to continuous improvement of the environment
* Ensure the platform remains understandable and maintainable by others
4. Required Skills and Experience
4.1 Platform Expertise (Essential)
* Hands-on experience building and maintaining environments
* Strong understanding of:
* Board architecture and hierarchy
* Column types and best practices
* Automations and dependencies
* Permissions and workspace structure
* Ability to design clean, scalable templates rather than one-off solutions
* Experience configuring dashboards and views for operational visibility
4.2 Process and Analytical Skills
* Ability to interpret process maps, workflow diagrams, and written designs
* Strong attention to detail and consistency
* Comfortable translating abstract requirements into structured builds
* Systems-oriented thinking, with an emphasis on data flow and integrity
4.3 Ways of Working
* Structured, methodical, and quality-focused
* Comfortable working within defined governance and standards
* Clear communicator who raises risks and questions early
* Disciplined about avoiding workaround-driven solutions
5. Desirable Attributes
* Experience supporting rollouts across multiple teams or functions
* Exposure to:
* Delivery or programme environments
* Operational reporting and dashboards
* Organisations transitioning away from spreadsheets
* Experience working alongside process or transformation consultants
6. Success Measures
The Platform Builder will be successful if:
* workflows accurately reflect agreed processes
* Proof-of-concept builds validate the intended design direction
* Boards and templates are clear, reusable, and easy to understand
* Data quality supports reliable reporting and decision-making
* Stakeholders trust as the system of record for delivery
* Holden can continue platform development independently after Phase 1
7. Role Context and Reporting
* Works closely with Holden programme leadership and process owners
* Day-to-day priorities guided by agreed plans and designs
* Collaborates with external advisors during Phase 1
* Transitions to internal platform ownership post-Phase 1
8. Role Evolution
Over time, the Platform Builder may:
* Take ownership of governance and standards
* Support rollout to additional functions or regions
* Develop more advanced automations and reporting
* Act as an internal centre of excellence for
9. Experience Profile
The successful candidate will typically have:
* 3–6 years' experience working with work-management platforms
* At least 2 years' hands-on experience building or administering
* Practical experience configuring:
* Boards, columns, automations, and permissions
* End-to-end delivery workflows
* Experience supporting operational or delivery teams within governed environments
Direct experience with is required.
The ability to work methodically from agreed designs, collaborate across functions, and maintain platform integrity as complexity increases is essential.