The Organisation Amgen GmBH
[eb_page_meta]Amgen is an American-based multinational biopharmaceutical company headquartered in Thousand Oaks, California. Located in the Conejo Valley, Amgen is the world’s largest independent biotechnology firm.
The brief [eb_page_title]
Rob has led an innovative and useful project for me over the last 6 months. He is a creative product lead and has designed and developed a tool that exceeded his brief.Peter Lanagan, Director Sales and Marketing T & D, Amgen GmbH
Having a fragmented set of marketing strategies based on differing metrics was leading to confusion when it came to measuring KPIs globally. Amgen were already in the process of unifying this into a single model but their biggest hurdle was understanding how to realign the mind-set and working practices of the global marketing workforce.
The brief was to create an application that would unify the brand building process across all key fields on a global scale. The application had to be intuitive with a minimal learning curve and yet retain all functionality, content and data.
The reality was that I was managing in-house developers and analysts as well as client-side architects spanning 3 continents to conceptualise, build and integrate something very unique and we were working to an eye-watering deadline.
Inception and product taxonomy
The key to success was to understand and map the various workflow process that each sector undertook to generate their individual KPIs. Once received, this was categorised into the varied content types, deliverables and responsibilities. This was then mapped into a matrix of responsibilities / deliverables against process stage and time and the exercise repeated for each geographic sector.
Getting the message across – Timelines
The interface and user experience artefacts, their taxonomy, placement, transitions between were all styled in the format of a linear parallax timeline. The primary timeline highlighting the end to end process ran across the top. It was functionally active and information driven meaning that end users could use it as a reference point to understand at which point in the governing timeline they were viewing and also to skip forward and back “in time” to see what should have been executed and what was to be.
The next level referenced a substage of the primary, again split into various key milestones within that stage. Lastly was the content section that gave relevant information as to what needed to be accomplished but whom and when in order to maintain the work flow. Again, this was keyed against a story, leading the user through what good looked like, through to templates of the required work for that stage, any action points resulting and meeting that should occur and finally guidance on completing the work and how it fit in to the grand scheme of things.