Template-driven content creation
Template-driven content creation
Team:
+
+
My contribution:
⚡ TL;DR
Creating custom event content used to require code skills and cross-device checks. I introduced reusable templates and in-context preview so that orgnizers could publish content confidently without technical skills.
📊 Outcome
78%
faster content creation
Measured by creating the same content using the legacy solution and new design.
Client Net Promoter Score (NPS)
6
10
One client who previously gave us a 6, citing poor content creation as the reason, later gave us a 10 after the update.
⚖️ Constraints and decisions
📌 After-release learning
Despite the fact that templates tested well in remote user testing, post-release feedback showed they did not scale in real use. As organizers attempted to customize content, the templates quickly became restrictive, which explains why many teams started with them but later removed most elements.
As planned, we started exploring reusable content blocks. However, engineering flagged that adding more customization to the existing editor would create tech debt and risk performance issues. Supporting reusable content blocks would require a new editor, effectively invalidating much of the template work. This exposed a significant scalability issue that was not identified during scope planning. Going forward, feasibility checks against long-term goals should be a core part of project planning, not a late-stage consideration.