we.watson was an internal product concept exploring a community and engagement layer for the watson news platform. The idea: give the watson audience a dedicated space to connect, discuss and participate — beyond the comment section.
I led the UX/UI design through research, concept, wireframes and high-fidelity prototypes. The project reached final design stage before being stopped due to a strategic reprioritisation. The final designs remain a strong reference for community-first product thinking within a news context.
watson's platform showed nothing of the people behind it — it was a product, with no place to meet the team.
we.watson was conceived as the answer: a home for team photography, culture and open roles, giving that content the room it never had on the news platform — and cleanly separating product from company.
Before a single screen was drawn, a series of workshops set out to answer the questions that would shape the whole platform: who is the audience for this new site? What do they need — and how do they behave? Is there untapped potential in our own content once the constraints of the watson.ch news platform fall away? Does the site need entirely new content? And how should a corporate site like this be structured and navigated?
Stakeholders from marketing, editorial, social media, analytics and senior management (GL) took part across several sessions. Together we developed personas and scenarios, mapped needs and pain points, and used the workshops to identify new content opportunities and shape the site's information architecture — arriving at a shared set of outputs: personas, scenarios, needs, pain points, content, structure and early design ideas.
The information architecture that came out of the workshops (left), and early content-structure ideas for each section — Werbung, Über uns, Karriere, News and Kontakt (right).
Two of the personas that came out of the workshops — Michelle, a prospective employee, and Kevin, a prospective advertising client — mapped through their scenarios, needs and pain points.
The information architecture and content decisions were translated into low-fidelity wireframes across every planned page. Everything — layout, content blocks, navigation — was built up through these wireframes first. From there, high-fidelity prototypes were developed and verified before the project reached final design stage.
Low-fidelity wireframes across every planned page.
The resulting high-fidelity prototypes, built out and verified across the homepage, Über uns, Werbung, Karriere and News.
The project was handed to development and the screen designs were practically final when it was stopped for strategic company reasons — a decision outside my remit, and one that meant it never saw a public release. The recordings below show the finished screen designs for the Werbung, Über uns and Karriere sections as they stood at handover.