Duplicating a Pathway

Duplicating a Harvard Business Publishing pathway is one of the most common actions a client admin takes when getting started on HBP Spark. The platform comes with a curated library of expert-designed learning paths. Admins don’t build from scratch — they start with something HBP made, make it their own, and publish it for their organization.

This sounds simple. It isn’t.

The moment you duplicate content, you have to make decisions about identity, ownership, and inheritance. Every attribute of the original pathway is a question: does this carry over? If so, does it stay linked to the original, or does it become independent?

The Identity Shift

The first and most important rule: when a client duplicates an HBP pathway, the duplicate’s type changes from HBP to “From Your Organization.” This is not a cosmetic change — it’s a fundamental identity shift. The content has moved from HBP’s canonical library into the client’s domain.

This matters for several reasons:

• The client now owns it. They can edit it. HBP changes to the original won’t propagate to the duplicate.
• Learners will see it as org-created content, not HBP content. That distinction affects how they trust and engage with it.
• The duplicate is subject to the client’s content lifecycle rules, not HBP’s.

Making this identity shift clear — both in the design and in the communications around it — was important for managing admin expectations.

Bookmarks Don’t Transfer

If the original HBP pathway is bookmarked by a user, the duplicate does not inherit those bookmarks. This might seem like a minor detail but it’s actually a principled decision: bookmarks represent a personal relationship between a user and a specific piece of content. Duplicating the content creates a new object. The new object has no prior relationships.

This also prevents the awkward situation where a user gets a notification about a pathway they thought they’d saved, only to discover it’s now someone else’s version with different content.

Skills Tags: An Important Nuance

NOT shown in the UI but specified in the flow: if the original pathway is tagged with skills, those skill tags carry over to the duplicate and appear in the Skills Dropdown in the Pathway Editor. Skills are metadata about content structure, not about organizational ownership. They’re worth inheriting.

This was a decision that came out of a specific use case: an admin duplicates a pathway on “Leading Through Change” and wants to keep the skill tags because they’re using the platform’s skill framework to organize recommendations for learners. If skill tags don’t transfer, the admin has to manually re-tag — a tedious step that would get skipped, degrading the quality of recommendations.

Completion Status: A Clean Slate

Here’s one of the more counterintuitive decisions: learner completion status does not transfer to the duplicate. If a user completed the original HBP pathway, that completion is tied to the original. When a duplicate is created, it’s a new object with no completion records.

The learner has to start the pathway fresh — “in order to track progress” as the spec notes. This might feel like a regression in some edge cases, but it’s the correct model. The duplicate is not the same pathway. It may have been edited. Its contents may have changed. Treating a completion of the original as equivalent to completing the modified duplicate would create inaccurate learning records.

Learning Activities Become Posts

One of the more technically interesting aspects of duplication: some content in HBP pathways lives as what the system calls “Learning Activities.” When a pathway is duplicated, these Learning Activities become “Posts” — the client-editable format that allows modification of content.

Critically, completion status for these converted posts does not carry over. The spec is explicit: “All Learning Activities that become Posts do not carry over the Asset Completion Status.” This is correct. If the content has been converted into an editable format, it’s no longer the same content. Previous completion of the original learning activity means nothing for the new post.

What This Flow Taught Me

Duplication seems like a copy-paste operation. In reality it’s an exercise in identity philosophy: what makes something “the same thing,” and what makes it new? Every attribute of the pathway forced a deliberate answer to that question. The result is a duplication behavior that’s predictable, principled, and consistent — even if no learner ever sees the logic behind it.

The best system behaviors are the ones users never have to think about. They just work the way you’d expect if you stopped to think through the logic yourself.