I’m not an engineer, but I’m pretty good at shaping and solutioning engagements outside of my domain, that are buyable and sellable, and I’ve come a long way since describing anything not related to strategy, experience or design as ‘connecting the pipes’.
I partnered with our Chief Portfolio Architect and Delivery and Account leads to shape, solution, present and sell 2 squads across 10 sprints for MVP 1 engineering of the wavespace experience design platform.
Research, personas, journeys and service blue-prints, sitemaps and detailed, annotated, dev-ready responsive designs were finally coming to life.
MVP 1 development will turn an older, manual system of creating a wavespace into a digital system that allows elite, design thinking experience managers and designers to review digitized activity catalogs and create a run-of-show schedules for their time with clients—reviewing . Users can review previous wavespace activity and see how others like them, run wavespaces.
The experience over the last 12+ months has been a ton of learning for me—about EY and their culture and critical stakeholder tours and presentations along the journey—and all from three distinct roles: BD lead, CD (internally) and an Executive Sponsor, across planning, research, strategy and POC-design. I think this is still my favorite agency role—early work in BD and relationship building, but also some mortar around the thing early, in Define & Design. Staying on and managing the team and the clock in Delivery helps me check the sometimes BS of BD.
Sometimes, there’s a belief that because technology (or cloud or managed services or even staff aug) is different than strategy or design, that it should be proposed and presented differently. I don’t tend to agree. I wrote and presented and sold in the same, known and tame manner, we have for the past year plus of Strategy, Definition, Planning and Product Design engagements. A good story works, regardless of the hero.
With dev-ready, annotated responsive designs at the ready, let the dev begin!