Link to Google Doc

Customer/User Job-to-be-Done or Problem

As a company, we need to maintain our brand and recognition within our products, and current Career Coach and SkillsMatch are using old domains, URLs, and behind-the-scenes services.

Value to Customers & Users

• Value for Clients:

  • Eliminate any confusion seeing out-of-date branding items might cause.

Value to Lightcast

• Brand consistency throughout our products helps to solidify our new name and identity.

Target User Role/Client/Client Category

Target Client/Client Category: Learner-facing product clients & potential buyers

Delivery Mechanism

Via Career Coach, Widget Builder, CC API Suite, and SkillsMatch

Success Criteria & Metrics

We are able to demonstrate that we represent Lightcast throughout Career Coach, Widget Builder, API documentation, and SkillsMatch.

Aspects that are out of scope (of this phase)

What is explicitly not a part of this epic? List things that have been discussed but will not be included. Things you imagine in a phase 2, etc.

n/a

Solution Description

In this final phase, we’ll tackle domains, URLs, APIs, service names, and taxonomies. Please see these Confluence documents by Kaleb Trotter for more information:

• Rebranding Initiative Overview

• Rebranding Initiative, Phase 3

Early UX (wireframes or mockups)

n/a

Non-Functional Attributes & Usage Projections

We need to keep the same accessibility and mobile responsiveness features that we have now and all performance characteristics should be the same.

Dependencies

I’m unaware of any dependencies for this work.

Legal and Ethical Considerations

n/a

High-Level Rollout Strategies

• Provide frequent updates within the CC Release Notes and EDU All Hands to communicate the status and results of this work.

• Once the redirect is live, let the Success team know that redirects are in place and the new default domains.

• The Success team can work with their clients to switch links, but the redirects will be in place for an extended period of time as they are needed for widgets and implemented clients.

Risks

• Confusion for users who get redirected to lightcastcc.com.

Open Questions

• How long do we need to keep emsicc.com active?

• What are the consequences for our CC API clients and their active calls?

Complete with Engineering Teams

Estimated Costs

Direct Financial Costs

Are there direct costs that this feature entails? Dataset acquisition, server purchasing, software licenses, etc.?

Team Effort

Each team involved should give a general t-shirt size estimate of their work involved. As the epic proceeds, they can add a link to the Jira epic/issue associated with their portion of this work.