Case study
Temple Kiosk Content
The problem
Temple kiosks needed accurate, up-to-date content, and that content lived across several teams, systems and outside vendors. Nobody had the whole picture.
My role
I was the Publishing Services liaison for temple kiosk content, the bridge between the Temple Department, the development and data teams, and the outside kiosk vendors.
The process
- Reverse-engineered the data. I worked out how the data in the different systems related to each other, so kiosk content could be populated dynamically instead of by hand.
- Analyzed the image workflow. I studied the workflow for temple images and recommended dropping a costly vignette requirement.
- Kept everyone talking. Translating between the Temple Department's needs, the developers and the vendors was half the job.
What I took from it
A lot of "technology problems" are really translation problems between teams.