Illustrative engagement. A representative scenario showing how we approach this kind of work in creative services. It does not describe a specific client; outcomes are described qualitatively.
Industry overview
What is shaping creative services
Design studios and creative agencies need evidence that their work performs, insight into their clients and research that helps them win pitches.
- Clients ask for proof that creative work performs
- Client relationships drive repeat business
- Talent is the main asset
Client background
A content production agency, working in India & UAE. This is an illustrative engagement: a representative scenario showing how we approach this kind of work, not a named client project.
- Organisation
- A content production agency
- Sector
- Creative services
- Team engaged
- IT & Development
- Services
- Web application development, UI/UX design
Client challenge
Feedback on creatives arrived by email and chat, so versions were lost and approvals were unclear.
Research objectives
- Deliver on the brief: a review and approval app for creative work.
- Design around the real needs of users.
- Define requirements and success criteria the solution would be tested against.
- Deliver a reliable, secure solution the team can run and extend.
Target audience
The work focused on 40 users.
- users40
Audiences we typically reach in creative services
Agency clientsTarget audiences for creative workCreative teamsProspectsFreelancers
Geographic coverage
Coverage: India & UAE. Markets: India and United Arab Emirates.
- India
- United Arab Emirates
Research methodology
An iterative delivery approach: discovery, design, build and test in short cycles, with the client reviewing each step.
- 1Brief
- 2Proofing tool
- 3Approval workflow
- 4Insight
We built a web app where clients comment directly on designs and videos, with version history and a clear approval step.
Web application developmentUI/UX design
Sampling strategy
- users
- 40
- Users and stakeholders from every affected team took part in discovery workshops and acceptance testing.
Data collection
- Requirements were gathered through workshops, process walk-throughs and a review of existing systems and data.
Data quality & validation
- Peer code review on every change
- Automated and manual testing
- User-acceptance testing with the client
- Release checklist and rollback plan
Data analysis
- Usage and performance monitoring after launch
- Defect and support-ticket trends
- Process time before and after
Key findings
- One place for feedback ends version confusion.
Recommendations
- Build on the core insight: one place for feedback ends version confusion.
- Track adoption and support tickets, and plan the next release from real usage.
Business impact
- Feedback rounds became shorter and approvals were recorded in one place.
Impact is described qualitatively.
Deliverables & next steps
- Cleaned data file and data tables
- Deployed solution with documentation and handover
- Support and maintenance plan
- Repeat the measure after changes are in place to track progress.
- A natural follow-on question: how satisfied are our clients?