Starting a Web Office From Scratch: Trials and Tales

695 views
632 views

Published on

Published in: Education, Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
695
On SlideShare
0
From Embeds
0
Number of Embeds
147
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Starting a Web Office From Scratch: Trials and Tales

  1. 1. Starting a Web Office from Scratch: Trials and Tales
  2. 2. committees, policies, guidelines
  3. 3. politics
  4. 4. Structure of team
  5. 5. function - services based agency / global function
  6. 6. department location - IT VS marketing vs hybrid Size of university matter? Quality of skill in each area matters Front end engineering, usability are key progressive in nature vs guarded
  7. 7. CMS - content / content providers Buy vs Build Workflow Content Creators are empowered Setting limits and sticking to them Training for best practices Not a silver bullet, doesn't fix people problems, doesn't write copy Be sure to enforce consistent style - writing, code, design
  8. 8. web groups
  9. 9. communication
  10. 10. project management Centralize email address vs service request form Project management takes a lot of time Streamlining and getting the most bang for the buck Time is finite, you can always add more people find what works for you, be sure everyone is comfortable and do it all in, halfway doesnt work
  11. 11. strategy / playbook
  12. 12. user centric
  13. 13. avoid bloat under do, they don't need all those features say no and make decisions based on need Be the expert, that is why they hired you, bring backup to statements you make out of date and inconsistent API's global directories Optimize for front end usage Cache Everything.
  14. 14. processes New Site vs. Redesign vs. Realign Everything starts with the needs and goals Then moves to navigation Then content Design, programming, testing Refactoring once content is placed is not a bad thing Internal team flow Openess Willingness to change What is efficent for others may not be for you
  15. 15. measurement / goals
  16. 16. challenge your team and your university to be better Higher Ed Web Galleries Internal Awards Stats and trends show progress Speaking and presenting to share your talent with others
  17. 17. 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 CMS Poorly written code can be exploited very fast Updates (esp security updates) need to happen often Align with those that are a voice of reason, identify early adopters and work with them
  18. 18. Questions?
  19. 19. Thank you. Nick DeNardis @nickdenardis nick.denardis@gmail.com Matt Herzberger @mherzber mherzberger@gmail.com

×