smorani
commented
11 years ago Don't know if your notes will be revealed but if so fix these typos: Under 2010 'Supposted' should be 'Supposed' Under 2011 for TODAY 'Beleived' should be 'believed' Under 2012 tense for 'Unsure of content strategy with ownership changed' should be 'change'
Some additional thoughts - take of it what you will, some of which you were likely already going to touch on:
In your 2008 slide, its worth mentioning that that's when we built a dedicated Site UI (eventually Foundry) team separate from the interactive team that allowed us to start thinking about foundation and site scalability.
Scalability as a value influenced our thinking in lots of areas. From section templates for the cover/fronts to show fronts to to video skinning for the player and interactive templates as well. And we did this for the sake of efficiency and maximizing the capabilities of a small team powering a large site and a finite budget. And focusing less on one-offs allowed us to iterate on products to improve design and add features (in my context - video - v1 player to larger more integrated v2 - exploring vatican keywording etc. and the creation of a story page player). Later we applied that sort of scalability thinking to the first set of iOS apps (2010?) that we developed in-house. And that exercise itself was a function of empowering the department to take a critical eye to what the gaps were and where some design/dev thinking (and awareness of industry trends) could boost the overall product and have a pro-active rather than re-active stance.
Worth noting that having our department being acutely aware of the business needs (working with Gabe and team on Ad Tiers, pushing for analytics - GA) and not sheltered helped us to frame our ideas not simply in a smaller puzzle of 'what looks good' but rather in a larger puzzle of what provides a great user experience as well as serving the business.
Encouraging that sort of critical thinking contributed to pushing us to our first crack at continuous consumption and responsiveness in streams/sliders.
With brand teams we still have a sense of scalability but recognize the need for a different audience context and different design for a branded look. But being part of a larger cohesive UX team allows us to share ideas, findings via analytics and ultimately code easily (blue interim design from sliders).
May also be worth mentioning how we have found greater efficiencies by partnering with technology to be more nimble and reduce large stakeholdering cycles by embracing agile processes.
colinhicks
dangerwells
luxuryluke
@chrisocast @colinhicks @smorani, I've added a folder to this repo with a draft of my slides for Wednesday. Notes are in the html as asides.
Please look this over and make suggestions on this issue about how to add some personality no later than 3pm ET Monday. Could be quotes added from staff, funny gifs, clarified points, etc.
As an (ehm) aside, I can't seem to get the speaker notes feature to work in reveal.js. The documentation says you just hit 's' or add a 'notes' query string. Doesn't work for me. Am I missing a plug-in?
Also, is it feasible to push this to Heroku? I don't know how.