Designed a Usage Web Tracker for collecting analytics.
We identified a problem where the usage processing metrics were seeing very low adoption by repository administrators, who use this service to capture metrics according to the COUNTER Code of Practice.
We initiated the project with a survey, conducted among key stakeholders, to ascertain the main difficulties associated with the current usage processing service, and to gauge the technical capabilities within the stakeholder groups. The survey, distributed across multiple networks and mediums, garnered 85 responses.
Based on the survey results, I drafted a potential design solution addressing the issues revealed by the survey. I then used a Request for Comments (RFC) feedback collection method via Productboard to gain feedback on the initial solution from DataCite's community members.
Analysis of both the survey results and RFC feedback enabled us to generate an MVP. An Expert Walkthrough was later conducted to validate the interaction design of the web tracker, with participation from 10 experts.
Cost of implementation was the main factor behind the lack of adoption
The organisation have low technical capabilities. A solution analogous to Google analytics would be welcomed.
The RFC indicated that we could augment the adoption rate of our usage service by a factor of five.
1. Development of a JavaScript web tracker, offering ease of implementation through a simple copy-paste mechanism.
2. Inclusion of a series of validation checks to discourage misuse and enhance the system's robustness.
3. Integration of the new solution with DataCite's existing user management system, Fabrica, to expedite user adoption.
1. I crafted a collection of wireframes in Figma for the prototype. Since the service is primarily developer-centric, I outlined a series of operational flows for the web tracker.
2. I also conceived JavaScript interface snippets to provide a frictionless Developer Experience.
3. The final deliverable comprised a Figma file and product specifications in Gherkin syntax, seamlessly transferred to the development team..
The adoption of Gherkin syntax for product specification effectively reduced the handover time facilitating the developers' transition to Test-Driven Development (TDD).
The refined process resulted in a threefold increase in user sign-ups for the new services.
Employing Gherkin for standardizing specifications proved immensely advantageous for our ongoing collaboration with the development team.
Furthermore, the RFC methodology yielded valuable insights from community members, despite them not being direct users of the service, thus enriching our understanding of our broader user community.