This case study explains how I led the end-to-end coordination of the Industry 5.0 Wiki for the Horizon Europe PROSPECTS 5.0 project - from early content architecture and functional requirements to partner onboarding, public launch, user feedback, QA, and ongoing development.
Live platform: wiki.prospects5-0.eu
This repository contains only public, portfolio-safe information. It does not include consortium-internal documents, personal data, credentials, or proprietary source code.
As the responsible project manager for INTRACT’s WP5 / Task 5.2 work, I:
- translated contractual commitments and stakeholder needs into a platform roadmap;
- defined the information architecture, content categories, contribution flow, and editorial rules;
- coordinated requirements and issue resolution with the web-development team;
- collected and managed contributions from 25 of 30 consortium partners;
- prepared templates and guidance and delivered partner onboarding;
- coordinated consortium review, stakeholder validation, and iterative improvements;
- served as the main author of the public Wiki deliverable; and
- continued platform governance, content curation, analytics review, and QA after launch.
| Stage | Main activities | Outcome |
|---|---|---|
| Discovery | Contract review, category design, partner commitments | Shared scope and information architecture |
| Definition | Templates, guidance, content calendar, functional requirements | Repeatable contribution process |
| Build | Developer coordination, navigation and feature reviews | Review-ready platform at M12 |
| Launch | Consortium review, corrections, communications | Public launch at M13 (January 2025) |
| Validate | Community survey, analytics, usability feedback | Evidence-based backlog |
| Improve | New sections, contribution forms, integration and QA | Continuously maintained knowledge product |
- 127+ articles across more than 10 content categories
- 127 registered users
- Contributions coordinated across 14 use cases and an international consortium
- Public launch delivered on schedule
- Stakeholder survey used to assess usefulness, navigation, content demand, and contribution intent
- Assessment Platform integration coordinated across project and software teams
- Search, authentication, download, commenting, reading-time, view-count, and contribution features
- One registration path for the community, Wiki contributors, and the self-assessment platform
- Clear “How to contribute” workflow with structured forms and mandatory metadata
- Separate pages for webinar and training-module content
- Defect handling for authentication, caching, account lockout messaging, image quality, and download controls
This is not a software-development portfolio piece. It demonstrates the work between research and software delivery: understanding the grant and methodology, defining usable requirements, coordinating dependencies, validating the output with users, and keeping the digital product aligned with contractual commitments.