Context & Problem Space
The business context
Diligent's governance platform serves clients with varying branding, layout, and configuration requirements. Before each client goes live, the implementation team applies a set of web customisations — visual themes, layout configurations, and display settings — to match the client's specifications.
The bottleneck
This customisation process was manual and repetitive. For every new client onboarding, an analyst would step through the same configuration workflow — applying settings one by one, verifying outputs, and documenting changes. The process repeated with minor variations across every client.
Target users
Primary: Implementation and Customer Success teams in Bengaluru who configure per-client customisations before go-live.
Baseline friction
- Repetitive manual steps for each new client onboarding
- Analyst time consumed by configuration work instead of client-facing activities
- Risk of inconsistency — manual application of settings varied by analyst
- No standardised workflow documentation for the customisation process
Discovery & Technical Constraints
How the problem was surfaced
This wasn't a top-down initiative. The bottleneck was identified through direct frontline experience — performing the customisation work repeatedly, recognising the pattern, and quantifying the time sink before proposing a solution.
Key constraints
- Solution needed to integrate with the existing customisation workflow — not replace it entirely
- Had to work within current tooling and permissions available to the operations team
- Needed leadership buy-in before any development could start
- One-quarter delivery window — had to ship fast to prove value
Solution & Product Ownership
Business case and PRD
Built the business case quantifying time spent on manual customisation across client onboardings. Authored the PRD with requirements, acceptance criteria, and a clear delivery timeline. Secured leadership sign-off before writing any code.
What was built
An automation tool that handles per-client web customisation — reducing manual steps to a streamlined, repeatable process. The tool was designed to fit directly into the team's existing workflow so adoption was immediate rather than requiring process change.
Execution & Cross-Functional Leadership
Delivery timeline
Shipped end-to-end within a single quarter — from business case presentation to working tool in production. The compressed timeline was deliberate: shipping fast proved the concept's value and earned continued investment.
Stakeholder alignment
Secured leadership sign-off on the business case before starting development. This meant the initiative had organisational backing from day one — not a side project that needed retroactive approval.
Adoption
The tool was adopted immediately into the team's standard workflow. No formal training rollout was needed because it was designed to mirror the existing process — just faster and more consistent.
Outcomes & Key Takeaways
Verified impact
72% reduction in per-client customisation time. The tool remains in active daily production use since 2025 — it wasn't a proof-of-concept that sat on a shelf.
Operational efficiency
Consistency at scale. Every client now receives the same quality of customisation output regardless of which analyst runs the process. The tool eliminated analyst-dependent variation.
Bandwidth reclaimed. Time freed from manual customisation is now spent on client-facing work — onboarding support, migration coordination, and platform adoption.
Key takeaways
1. Frontline teams see the automation opportunities first. This initiative came from doing the work — not from a strategic planning session. The people closest to the repetitive process are best positioned to identify what can be automated.
2. A business case gets further than a prototype. For the BoardDocs tool, I built first and earned scope after. For this tool, I led with the business case and secured buy-in before writing code. Both approaches work — the right one depends on how much organisational investment is required upfront.
3. Design for zero friction adoption. The tool mirrors the existing workflow. No new processes, no training sessions, no "change management." Adoption happened on day one because the tool felt like a faster version of what the team was already doing.