Skip to content

Story 0%Less motion

One portal. A connected ecosystem.

A provider home connecting product publishing, integrations, trust information, and partner services.

Edtech
providerA tool. A point of entry.

A maintained presence
for a provider’s tools.

PrivacyAccessibilityEfficacy evidence

Provider purchasesESSA evaluationsRevenue for the
Instructure partner program

Conceptual map of participation

Partner Portal

One place for providers to manage product information, integrations, evidence, and partner services.

EdCo Marketplace
A shared marketplace where educators discover and evaluate edtech tools, and providers showcase their products and connect with prospective customers.
Canvas LMS
A learning management system connecting teaching, learning, and edtech tools across K–12, higher education, and professional learning.
Impact
Usage analytics and in-app guidance that help institutions understand and improve adoption of their LMS and connected edtech tools.
LearnPlatform
An edtech management platform for organizing tool libraries, reviewing privacy and compliance, tracking usage, and evaluating effectiveness through ESSA-aligned research.

Provider UX mapping / Original project artifact

PHASE 3

Bring partners across.

New login routes from sunset products
User migration and program rebrand
Email and notification suite

PHASE 4

Support continued use.

UI tagging and behavioral reporting
In-app guidance
Support documentation overhaul

Product leadership / 9 months

Lead the work from discovery to launch.

I led the Partner Portal lifecycle from research and development through go-to-market.

Cross-product coordination
Four delivery phases
Marketplace launch + portal retirement

Adoption after launch

MAA 75.00%MAU 65.18%

December · MAA 75.00% · MAU 65.18%

8new features became among the most-used.

MAU: monthly active users. MAA is the source’s account label; its definition needs confirmation.

Original product collage used as the Partner Portal video cover.

Watch the full portal demoSee the complete product in use

MY ROLE

Product leadership from discovery through launch.

9 months · 4 delivery phases
5 engineers · 1 designer · PM

A provider publishing platform and a channel for paid partner services.

Product leadershipResearch to launch

Scroll through the work and its impact

The work behind Partner Portal

Lead the work from discovery to launch.

I led the Partner Portal lifecycle from research and development through go-to-market.

Product Manager working with five engineers and one designer over nine months.
Phased planning and coordination across product teams.
Simultaneous launch with the new Marketplace and retirement of legacy portals.

Understand the work before unifying it.

I developed partner personas to prioritize requirements around provider needs.

The project combined interviews and workflow mapping with providers and internal stakeholders.
Personas spanned integration-focused vendors and evidence-driven providers.
Workshops prioritized profile completion, evidence publishing, and integration management.
Market analysis and user research continued during development.

Define a shared asset workflow.

I led the creation of a central portal for partner assets and cross-product synchronization.

The first phase established central asset management and synchronization across products.
The product record brought provider information and assets into one managed surface.
The original prose references five interconnected products; its diagram names four destinations, reproduced here without adding a fifth.

Turn provider needs into capabilities.

Provider research and market analysis continued alongside the phased development work.

The second phase included integration tools, direct requests, and asset sharing.
The same phase also introduced evidence containers and monetization options.
The workflow map provides context for the product scope; it is not a dated phase milestone.

Make evidence part of the working record.

The scope connected provider needs with the information institutions use to evaluate tools.

Evidence containers are explicitly listed among the capabilities developed in phase 2.
The original journey map follows identifying missing vetting resources, requesting them, adding them, and approving access.
The new portal supports publishing efficacy evidence; the Evidence screen includes ESSA-aligned evidence and a connection to the evidence team.

Include the commercial role in the product.

The portal served provider workflows and the partner program’s business goals.

The published phase description identifies monetization options as part of phase 2.
The project owner identifies paid partner services, including ESSA evaluations, as the commercial model.
The case provides no quantified revenue amount, conversion rate, or attributed revenue growth.

Lead the transition into daily use.

Phased planning connected the Marketplace launch with legacy portal retirement.

Phase 3 introduced a new login experience routing users from sunset products, user migration, the partnership-program rebrand, and email/notification updates.
Phase 4 introduced third-party UI tagging and reporting for adoption, friction, attrition, and preferred paths.
In-app guidance and a support documentation overhaul supported adoption.
These were delivered capabilities; the source does not quantify reductions in friction or attrition.

Connect delivery to the outcome.

A provider publishing platform and an operating foundation for the partner program.

The original graph reports monthly values from July launch through December, without a year.
The graph labels the account series MAA; surrounding prose also calls it total accounts. Its definition and calculation need confirmation.
The source reports eight new features among the application’s most-used.