becoming open behind closed doors

13
Becoming Open Behind Closed Doors Stratos Filalithis Head (Acting) of IS LTW Website & Communications

Upload: stratos-filalithis

Post on 07-Jan-2017

73 views

Category:

Education


0 download

TRANSCRIPT

Page 1: Becoming open behind closed doors

Becoming OpenBehind Closed Doors

Stratos FilalithisHead (Acting) of IS LTW Website &

Communications

Page 2: Becoming open behind closed doors

IS LTW Website & Communications

• University Website• University Web Search• User Training & Support• Community Management• UX & Digital Strategy Consultancy &

Research• Technical Solutions Implementation

Page 3: Becoming open behind closed doors

What we ‘re trying to get away from

IS Polopoly Service

UWP-led, centrally managed website

framework

IS Drupal Service

Unit X

Event

Y

Project

Z

Other Platforms & Services

SchoolB

SchoolA

InstituteC

Page 4: Becoming open behind closed doors

University Website (EdWeb)

• Front-end (http://www.ed.ac.uk)• Back-end Web Content Management System• EdWeb Distribution• Powered by Drupal

• EdWeb Change Management (CAB)

Page 5: Becoming open behind closed doors

EdGEL• Digital Design Framework, similar to

http://www.bbc.co.uk/gel• Sets standards for

– Graphic Design Elements– Enterprise-level Branding– UX– Accessibility– Technical delivery

• Powered by Twitter Bootstrap

Page 6: Becoming open behind closed doors

What we had planned for

Central Infrastructure

IS-led, centrally managed website

framework

Local Infrastructure

CollegeZ

Supported EdWeb Core

SchoolB

Local Code Development

Central Training & Support Local Training & Support

Central User Administration Local User Administration

EdGEL Local Theming & Styling

EdWeb Distribution

Unit X

EventY

SchoolA

Page 7: Becoming open behind closed doors

What if…– There was a public service road map to help people identify the future?– Service/College/School feature prioritisation could feed into a master list

of prioritised requirements?– System enhancement costs could be shared in all parts of the University?– There were clear change processes allowing direct user feedback?– Developers could code locally to feed into the central system?– We shared knowledge & experience?– We stopped resolving issues in isolation, eliminating duplicate effort?– Move away from our silos and work together?

Page 8: Becoming open behind closed doors

https://www.pinterest.com/pin/402790760400639619/

Page 9: Becoming open behind closed doors

Workshops

Page 10: Becoming open behind closed doors

EdWebCollaborativeFramework

* work in progress *

Page 11: Becoming open behind closed doors

EdWeb Code Sprint• Sprinting towards

a new goal (blog post): http://edin.ac/2bLX3hr

Page 12: Becoming open behind closed doors

Next steps• Map areas of focus

• Service-led• Community-led

• Secure funding (always helpful)• Engage relevant stakeholders to pilot processes

• Continue to think/act/plan in the same way…• Being open & review often

Page 13: Becoming open behind closed doors

Thank you!– Contact me: [email protected]