TDIC Website MVP Challenges
Identified risks
Scope for UX and Design work to the level detailed for MVP will take approximately 101 days; this is fast tracking, taking shortcuts and dedicating 100% of our time exclusively to this project. Not even a third of that time is being accounted for in the proposed schedule. Additionally, crucial tasks are missing from the project charter.
Phase 3: Execution - Design | 12/02/20 | 06/22/21 | |
Part 1: Discovery | 17d | 12/02/20 | 12/19/20 |
User research | 2d | 12/19/20 | 12/21/20 |
Competitive analysis | 2d | 12/21/20 | 12/23/20 |
Content audit | 10d | 12/23/20 | 01/02/21 |
Prepare findings for stakeholder presentation | 1d | 01/02/21 | 01/03/21 |
Stakeholder review & approval | 2d | 01/03/21 | 01/05/21 |
Part 2: UX Strategy | 32d | 01/05/21 | 02/06/21 |
Stakeholder workshop: Content prioritization | 2d | 02/06/21 | 02/08/21 |
Information architecture | 7d | 02/08/21 | 02/15/21 |
Stakeholder workshop: User journeys | 1d | 02/15/21 | 02/16/21 |
Navigation and User/customer journeys | 7d | 02/16/21 | 02/23/21 |
Stakeholder workshop: Task flows | 1d | 02/23/21 | 02/24/21 |
Content strategy | 7d | 02/24/21 | 03/03/21 |
Metadata | 7d | 03/03/21 | 03/10/21 |
Part 3: UX Design | 31d | 03/10/21 | 04/10/21 |
Use cases and task flows | 7d | 04/10/21 | 04/17/21 |
Low-fidelity wireframes | 7d | 04/17/21 | 04/24/21 |
Content revisions | 3d | 04/24/21 | 04/27/21 |
Low-fidelity prototypes | 7d | 04/27/21 | 05/04/21 |
User focus groups and/or testing | 7d | 05/04/21 | 05/11/21 |
Part 4: Production Visual Design & Development | 21d | 05/11/21 | 06/01/21 |
Design System / Branding | 7d | 06/01/21 | 06/08/21 |
Visual elements (photography and video) | 7d | 06/08/21 | 06/15/21 |
High-fidelity mockups/prototypes | 7d | 06/15/21 | 06/22/21 |
101d |
Given the timeline above, which tasks are we willing to skip/sacrifice? As proposed, the project is liable to cost time and money to our business unit by having to rectify preventable errors and misdirections.
Additional Risks
Azure implementation scheduled to happen before deployment
Development set to happen before an instance of DNN is established
No inclusion of structured content (such as 2sxc) in the plan charter
2sxc is crucial for our team to be able to build the 150+ pages in tdicinsurance.com. At an hour per page, we’re looking at a minimum of 150 hours JUST for page building. Contrary to what’s stated in the project plan, content cannot be “copied, ported or migrated”. All elements must be rebuilt from scratch; using 2sxc makes this process doable without having to use a front end developer for the task. As is, we only have 2 people in the project that are capable to use 2sxc to create content.
No proposed UX testing until after full development
This is anathema to Agile methodology and creates a huge risk of spending large amounts of money and time on a site that might have UX problems that can only be identified through testing.
Project charter mentions video content and photo content to be developed in parallel to this work; is this to be outsourced to a separate team?
Resource allocation is limited for TDIC: will we have additional staff that can help with UX, content strategy, design and implementation?
TDIC Website MVP Scope Proposal
May Release
Content Audit (page consolidation)
2sxc structured content implementation
Fluid width implementation
Home page redesign
Second level pages redesign (3)
UI Kit
PW reset
T&C’s version control
Portal integration
October Release
User behavior research
Content Strategy
Information Architecture: Entry points, navigation, regional split consolidation
User journeys
Task flows
Form changes (beyond what’s already in motion)
Theme changes
Style Sheet changes
Appointment Interface
User Calendar