starting a web office from scratch: trials and tales

19
Starting a Web Office from Scratch: Trials and Tales

Upload: nick-denardis

Post on 28-Nov-2014

911 views

Category:

Education


1 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Starting a Web Office From Scratch: Trials and Tales

Starting a Web Office from Scratch: Trials and Tales

Page 2: Starting a Web Office From Scratch: Trials and Tales

committees, policies, guidelines

Page 3: Starting a Web Office From Scratch: Trials and Tales

politics

Page 4: Starting a Web Office From Scratch: Trials and Tales

Structure of team

Page 5: Starting a Web Office From Scratch: Trials and Tales

function - services based agency / global function

Page 6: Starting a Web Office From Scratch: Trials and Tales

department location - IT VS marketing vs hybrid

Size of university matter?Quality of skill in each area mattersFront end engineering, usability are keyprogressive in nature vs guarded

Page 7: Starting a Web Office From Scratch: Trials and Tales

CMS - content / content providers

Buy vs BuildWorkflowContent Creators are empoweredSetting limits and sticking to themTraining for best practicesNot a silver bullet, doesn't fix people problems, doesn't write copy Be sure to enforce consistent style - writing, code, design

Page 8: Starting a Web Office From Scratch: Trials and Tales

web groups

Page 9: Starting a Web Office From Scratch: Trials and Tales

communication

Page 10: Starting a Web Office From Scratch: Trials and Tales

project management

Centralize email address vs service request formProject management takes a lot of timeStreamlining and getting the most bang for the buckTime is finite, you can always add more peoplefind what works for you, be sure everyone is comfortable and do it all in, halfway doesnt work

Page 11: Starting a Web Office From Scratch: Trials and Tales

strategy / playbook

Page 12: Starting a Web Office From Scratch: Trials and Tales

user centric

Page 13: Starting a Web Office From Scratch: Trials and Tales

avoid bloat

under do, they don't need all those featuressay no and make decisions based on needBe the expert, that is why they hired you, bring backup to statements you make out of date and inconsistentAPI'sglobal directoriesOptimize for front end usageCache Everything.

Page 14: Starting a Web Office From Scratch: Trials and Tales

processes

New Site vs. Redesign vs. RealignEverything starts with the needs and goalsThen moves to navigationThen content Design, programming, testingRefactoring once content is placed is not a bad thingInternal team flowOpenessWillingness to changeWhat is efficent for others may not be for you

Page 15: Starting a Web Office From Scratch: Trials and Tales

measurement / goals

Page 16: Starting a Web Office From Scratch: Trials and Tales

challenge your team and your university to be better

Higher Ed Web GalleriesInternal AwardsStats and trends show progressSpeaking and presenting to share your talent with others

Page 17: Starting a Web Office From Scratch: Trials and Tales

rouge faculty/staff will always test their limits

Give someone an inch and they will take a mile.Allowing PHP, Script or other tags in your CMSPoorly written code can be exploited very fastUpdates (esp security updates) need to happen oftenAlign with those that are a voice of reason, identify early adopters and work with them

Page 18: Starting a Web Office From Scratch: Trials and Tales

Questions?

Page 19: Starting a Web Office From Scratch: Trials and Tales

Thank you.Nick DeNardis@nickdenardis

[email protected]

Matt Herzberger@mherzber

[email protected]