Strong case studies use evidence: a real starting point, the work completed and a result that can be verified. Until a customer has approved the publication of their name, project details and outcomes, we will not invent them. This framework shows the process Stardetha uses to turn future projects into useful, honest case studies.
1. Establish the starting point
We begin by recording the business goal and the current website’s condition. Depending on the project, evidence can include screenshots, page speed measurements, search visibility, enquiry data, support complaints and observations from mobile usability testing. We also note the measurement period and limitations.
2. Define the customer problem
A weak case study says, “The old site looked outdated.” A useful one explains what that meant: customers could not find the right service, staff received unsuitable enquiries, key pages were difficult to use on phones, or the team could not update content safely.
3. Prioritise the work
We separate essential fixes from enhancements. A typical improvement plan may address:
- Clearer positioning and calls to action.
- A simpler navigation and page hierarchy.
- Responsive layouts for mobile and short laptop screens.
- Faster, properly sized media.
- Customer proof and reassurance near enquiry forms.
- Reusable editing controls for routine updates.
- Backups, security and measurement foundations.
4. Explain the implementation
The finished case study should connect each change to the original problem. It should also disclose important constraints and avoid claiming that one design change caused every improvement. Where possible, use before-and-after examples that protect confidential customer information.
5. Measure outcomes over time
Relevant outcomes may include qualified enquiries, completed purchases, form completion, task success, content-update time or site reliability. We choose metrics before launch, compare similar periods and distinguish measured results from customer observations.
6. Obtain approval
The customer should review their name, quotations, results and screenshots before publication. Sensitive details can be anonymised. If permission is limited, we state that clearly rather than presenting an illustrative story as a named customer success.
If you would like your website to become a future evidence-based Stardetha case study, explore our web design approach and tell us what is not working today.