News.fiu.edu
Migrated a legacy portal built on a WordPress template (~8 years old) that created barriers for editors when telling the stories.
Number of editors: 40 +, stories per week: 20 β 25.
Approached the project as a product by focusing on the challenge at hand rather than a βre-designβ or βmigrationβ.
Lead the team through a UX Research phase to identify pain points by conducting user interviews, surveys and feedback sessions.
Milestones
Phase 0: current solution assessment and decision between remaining in a WordPress template vs. bringing the solution into a custom-built template in the institutionβs content management system (CMS).
Flexibility to build components using the same technologies the team uses on a daily basis; avoiding the need to shift into a WordPress setup and technologies.
Workflows ability for editors, publishers, and administrators.
Agility to scale the site by iterating on components and layouts vs. use of 3rd party plugins.
Removed dependencies on 3rd party solutions β in many cases they were outdated, and the stories had holes over time as a consequence.
Phase 1: UX Research
Coordinated this phase to conduct surveys (intercept), user interviews and feedback sessions in collaboration with our interaction designer.
Assisted in removing barriers to empower the team to focus on the challenge rather than logistics.
FIU News + FIU Magazine β as one site, smooth as possible.
Phase 2: MVP
Information architecture established, led by our content strategists.
Feedback sessions on the MVPβs prototype.
Phase 3: Deployment, training, validation and analysis
news.fiu.edu π (2019)
Phase 4: iteration to include admin tools
Admin portal created to manage drafts and reporting on a monthly basis β built internally for the team.
Phase 5: iteration to release new component and assess list of pending features
Decided to halt the production cycle since the site was performing successfully and the learning curve for editors had been successfully completed.
Many of the items in the list of features sounded like great ideas but they were not a fit in regard to the editorβs skillset or timelines.
Phase 6: On-going support and minor iterations
Addition of new components on specific stories like a video banner embed and analysis to determine if it would be made available for all editors vs. a particular story.