PERSPECTIVE · UNIVERSAL TALENT PASSPORTS & THE FUTURE OF WORK
The Future of Talent Management
Starts With a Better Partnership.
People need continuity. Organizations need context. Both need a reason to share.
A Universal Talent Passport changes the starting point: the person’s experience can continue across roles and institutions, while each organizational relationship has a defined purpose and boundary.
Originally published October 3, 2023; revised September 13, 2026. This article presents Gobekli’s design principles and product vision, not a claim that every described workflow is available. See current product availability.
A career continues. Its records keep starting over.
An application describes one version of a person. A learning system records a course. A project tool records an activity. A manager hears the explanation behind a difficult decision.
Each has a useful part of the picture. When someone changes roles or leaves, reconstructing that experience can become their next task.
Our view is that a better model must serve two needs together: the individual’s ability to understand and carry their experience forward, and the organization’s need to understand the work it is responsible for.
A passport provides continuity. A relationship defines the exchange.
For the person
A continuing account of experience, learning, contribution, and goals—with a voice in how they are represented.
For the organization
Relevant context about responsibilities, capabilities, and needs—with clear sources and accountable decisions.
TalentPass is intended to support the individual side of that relationship. It should not require a person to begin their professional story again whenever an institution changes.
That continuity does not mean every employer receives a complete personal record. Sharing needs a purpose, an appropriate scope, and rules people can understand.
Three kinds of information. Different responsibilities.
Personal
Private reflections, undisclosed goals, and selected experience outside the organizational relationship.
Design principle: organizational access should not be automatic.
Organizational
Business records, internal operating information, and decisions managed through the organization’s systems.
Design principle: a personal passport does not replace institutional responsibilities.
Shared
Selected contributions, learning, feedback, and commitments exchanged for a defined purpose.
Design principle: clarify source, access, use, correction, and what can travel onward.
These are useful design distinctions, not a blanket determination of legal ownership. Rights, responsibilities, and access arrangements depend on the record and its context.
Useful intelligence should
give value back to the people creating it.
Recognition. Relevant opportunities. Better support. A record of growth they can appropriately carry forward.
What does the person get in return?
If an employee is asked for richer context, the organization should be able to explain how participation helps them—not only what it adds to a report.
A voice in the account
A chance to explain contributions, add context, and question an incomplete interpretation.
A useful response
Recognition, preparation, feedback, or a realistic next step connected to what was shared.
Appropriate continuity
Learning and experience that remain useful beyond one assignment or relationship.
Visible follow-through
Agreed support and actions that someone takes responsibility for carrying out.
These are commitments to design and evaluate. Collecting more data alone does not establish trust, engagement, or better outcomes.
The relationship changes across a career.
| Moment | What the person may contribute | What the organization should clarify or provide |
|---|---|---|
| Applying and joining | Relevant experience, learning, and supporting examples. | Work requirements, review criteria, and starting support. |
| Doing the work | Contribution, decisions, collaboration, and questions. | Responsibilities, feedback, recognition, and a route to resolve problems. |
| Learning and moving internally | Selected interests, experience, and evidence from practice. | Real opportunities, preparation, time, and transparent next steps. |
| Leaving or changing the relationship | A choice about future contact and appropriate information sharing. | Clear access changes and arrangements for records the person may retain or receive. |
The table describes an intended model, not automatic data transfers. At every transition, the purpose and recipients may change.
Passport Pages connect the relationship.
Gobekli uses Passport Pages to describe purpose-specific experiences for exchanging selected information between people, organizations, and supported sources.
An application, development conversation, or learning program may each need different information. The shared view should distinguish what the person supplied, what a source issued, what a reviewer concluded, and what AI suggested.
Define the request
What is needed, why, and by whom?
Keep the source visible
What does this record establish, and what remains interpretation?
Define the next use
What happens to the information when the purpose or relationship changes?
Existing HR, learning, and recruiting systems may retain their roles. Supported exchanges, controls, and verification methods need to be confirmed for the implementation.
Private reflection and organizational analysis need different boundaries.
A person might use Pythia to prepare for a conversation, reflect on experience, or consider a possible change. The design principle is that those private questions should not automatically become employer intelligence.
Organizational assistance in TalentSync serves a different purpose: examining work, responsibilities, and relevant shared context. Implementations must explain what information is accessible in each setting and how it may be used.
AI-generated interpretations should remain distinguishable from source records and human statements. People need a route to correct them, and consequential decisions need accountable review.
The value grows through a feedback loop.
Describe
People and organizations clarify the goal and what they need to understand.
Experience
Work and learning create contributions, outcomes, and new questions.
Interpret
People examine examples, evidence, feedback, and uncertainty.
Act and revisit
Someone responds, the work changes, and the next experience informs another review.
This is the broader ambition of the Human Intelligence Layer: organizational learning connected with individual development. A static profile is one view into that process, not the whole process.
When AI changes a task, the relationship still matters.
Consider a team using AI to draft customer responses. The job titles may stay the same while people spend more time checking exceptions, correcting context, and deciding what should be sent.
Understanding that change requires more than tool-usage counts. Employees can explain the judgment and effort involved; organizational records can show parts of the workflow. Together, those perspectives could inform responsibilities and support.
The aim is to help people participate in that change and carry their learning forward. It is not a rationale for monitoring every action or treating private reflections as a new data source.
How Gobekli is building toward the model.
TalentSync
The organizational context around people, work, capabilities, and needs.
Profiles and Talent Tree
Purpose-specific views and questions about capabilities in context.
Pythia and Passport Pages
Reflection and clarification, alongside defined exchanges.
This is a product vision at different stages of development. It does not promise universal portability, complete integrations, or automated employment decisions. Current options and any proposed engagement need to be reviewed against the available scope.
Make the terms of participation understandable.
- What information is requested, and which parts are optional?
- Who can access it, and which decisions may use it?
- How are corrections, disagreement, and AI suggestions handled?
- Which records may be retained or carried forward?
- What changes when employment or participation ends?
These questions belong in the design of the relationship. A downloaded copy may remain after a link is withdrawn; information rights and retention requirements need to be handled explicitly rather than implied by the word “control.”
Questions about the partnership model
What is a Universal Talent Passport?
In Gobekli’s vision, it is a person-centered, continuing account of professional experience, learning, and contribution. Supported features and portability options depend on the current product and participating systems.
Does an employer get access to the whole passport?
That is not the intended model. Selected information should be exchanged for a defined purpose with appropriate access arrangements. Confirm the available controls for a specific implementation.
Does a passport replace an employer’s records?
No. Organizational systems retain their own responsibilities. Personal continuity and organizational recordkeeping need clear boundaries rather than an assumption that one replaces the other.
What happens when someone leaves?
The intended model supports appropriate continuity of learning and experience while changing organizational access. What may be retained, issued, or shared must be defined for the actual records and relationship.
Is the full model available now?
No. This article describes design principles and broader product vision. Review the product-availability page and confirm the scope of any engagement.
Where should an organization start?
Choose one exchange where employees and the organization could both benefit. Define the purpose, sources, boundaries, and response employees should receive, then evaluate that scoped process.
Build a relationship
that helps both sides grow.
Start with one useful exchange—and a clear reason for people to participate.