HumaMap is not a new personality theory
HumaMap Core gives every Personal HumaMap a common structure, but HumaMap does not present CAN, WILL and HOW as a newly validated personality model. The structure is a product architecture for organising professional context around three practical questions: what can this person bring, what matters to them at work and how do they tend to work.
The architecture is informed by established work on capabilities, work styles, motivation and performance, but the HumaMap labels are our way of making that information usable rather than a claim that the three labels constitute a proprietary psychological theory.
Occupational information already separates skills from work style and context
O*NET, sponsored by the U.S. Department of Labor, organises occupational information across both the worker and the work. Its current Content Model separates abilities, skills, knowledge and experience from work styles, work activities and work context. O*NET also publishes explicit linkages between work styles and contextual features of work.
HumaMap does not copy the O*NET taxonomy. The relevance is conceptual: professional contribution cannot be understood only through experience and skills. How people approach work and the environment in which they do it also matter.
People make more sense in context
HumaMap's relational layer is consistent with the person-environment tradition in organisational psychology. A major Annual Review describes a central premise of person-environment fit theory: considering the person and environment together can explain outcomes better than treating either one alone.
HumaMap applies that principle cautiously. FIT is not a fourth person score. It is the relationship between Person, Work, Team and Company or Situation. A person who works well in one context can experience friction in another without either the person or context being universally “bad”.
Why CAN, WILL and HOW are kept separate
Separating CAN, WILL and HOW helps avoid mixing different questions into one judgement. CAN covers capabilities, knowledge, experience and learning or problem-solving capacity. WILL covers professional priorities such as ownership, learning, change and direction. HOW covers observable ways of working such as decisions, execution, communication, collaboration and leadership.
This also helps distinguish disposition from behaviour. Being open to change is not the same thing as how someone actually behaves when plans become uncertain. Wanting leadership responsibility is not the same as how someone leads in practice.
Evidence and reflection are different layers
HumaMap can allow a person to add recognised assessments, such as Big Five instruments, as optional evidence. Reflection frameworks can also be added when a person finds them useful. HumaMap keeps those sources separate because they are not the same type of claim.
A validated assessment should not be presented as equivalent to a reflective typology. Likewise, a reflection framework should not be dismissed simply because it serves a different purpose. The product should make the source and status visible so users can decide how much weight to place on it.
Team views should not become team types
Research on teams shows that effective teamwork depends on multiple interacting processes, and recent work on team charters emphasises the value of making roles, responsibilities and ways of working explicit. HumaMap therefore builds team context from the individuals and relationships underneath it rather than assigning the team a fixed personality label.
The practical outputs focus on complementarity, possible friction, what may be missing and what the team should make explicit. These are prompts for conversation and coordination, not deterministic predictions.
Role clarity and ownership matter independently of personality
Some team problems are structural rather than psychological. Meta-analytic research has repeatedly linked role ambiguity with poorer outcomes, and a 2026 review of six decades of role-stressor research identified role ambiguity as especially damaging among the stressors studied.
This matters for HumaMap because better people understanding should not be used to explain away unclear systems. If ownership is ambiguous, the first intervention may simply be to clarify responsibility and decision rights.
Human centricity and resilience are European business ideas, not just HumaMap language
The European Commission's Industry 5.0 vision explicitly adds human centricity, resilience and sustainability to the industrial conversation. It argues that technology should create value beyond efficiency alone and place worker wellbeing at the centre of transformation.
HumaMap aligns most directly with human centricity and resilience. The product aims to help companies use technology to understand people as individuals while retaining useful professional context through organisational change. HumaMap does not claim endorsement by the European Commission or that using HumaMap automatically makes a company Industry 5.0 compliant.
AI should help organise context, not hide responsibility
Ask HumaMap is HumaMap's AI assistant. It can use HumaMaps and reports a user is allowed to access to help explain professional context. The product principle is that AI may retrieve, connect and explain information, while people remain responsible for hiring, leadership and other people decisions.
This also supports transparency. The European Commission's Article 50 guidance under the AI Act requires people to be informed when they are directly interacting with an AI system in applicable cases. Ask HumaMap is therefore identified as AI rather than presented as a human adviser.
Employment use requires careful product boundaries
AI use in employment is a regulated area in Europe. Whether a particular system falls into a high-risk category depends on its intended purpose and how it is used. HumaMap therefore needs clear product boundaries around hiring and other consequential employment use.
The marketing and product principle is not enough on its own to determine legal classification. HumaMap should not quietly evolve into an automated candidate ranking or filtering system without reassessing the legal, product and governance implications. This is an area for ongoing legal and technical review.
Privacy begins with the scope of the data
HumaMap is designed as a professional work profile. The product rule is that HumaMap must not collect, require, infer or use GDPR Article 9 special category data as part of HumaMap profiles. This includes health information, political opinions, religion, trade-union membership, sexual orientation, race or ethnicity, genetic data and special-category biometric data.
That rule has to be enforced in the product, not only stated in marketing. Product inputs, uploads, AI processing, storage, logs and retention rules should all support the same narrow professional scope before this is treated as a verified technical guarantee.
What HumaMap does not claim
- HumaMap does not claim that a profile fully explains a person.
- HumaMap does not claim there is one universally good work style or personality.
- HumaMap does not claim CAN, WILL and HOW is a newly validated personality model.
- HumaMap does not claim optional reflection frameworks have the same evidentiary status as validated assessments.
- HumaMap does not claim to predict a particular hiring, team or business outcome.
- Ask HumaMap does not make hiring or leadership decisions for the user.