There’s a kind of anger that builds up over time. It comes from watching talented people go unnoticed. It comes from seeing teams struggle to explain what someone is actually good at. It comes from watching hiring managers, coaches and even the people themselves make guesses about ability of truly understanding it. That anger is real. That anger is what led me to create CapabiliSense.. That same anger is why I chose to share the entire journey on Medium instead of keeping it quiet while I worked on it.
If you’ve ever wondered why I’m building CapabiliSense or why I’m doing it publicly on Medium of keeping it under wraps this article is my answer. I get asked this question all the time: why CapabiliSense? Why share it on Medium? Why not keep it private?
I want to take you through the problem I kept running into. I want to show you what I saw in the tools we already have. I want to walk you through the ideas that are shaping how I’m building this product. I want to give you examples of the change I hope to bring.. I want to talk about where I think this is going.
I won’t pretend I have it all figured out. I don’t.. I do have a strong reason, for building CapabiliSense.. I think that reason—combined with why Medium is the right place to share it—is worth explaining clearly from the start.
The Problem That Wouldn’t Leave Me Alone
Before I ever wrote a line of code for CapabiliSense I spent a lot of time watching and thinking. I saw that people are really bad at explaining what they are good at. Not because they don’t have skills. Because most of us never had a way to see our own abilities clearly. We use job titles, resume points or yearly reviews that don’t show the whole story.
I saw the issue from a different angle too. Managers and team leaders often don’t understand the range of skills in their teams. They know who is good. They can’t always say why or in what areas. Capability, in companies is seen as something unclear and informal. It stays inside peoples heads of being tracked understood and improved on purpose.
This problem shows up everywhere:
- People who have the skills but can’t explain them in the way employers are looking for.
- Teams that do the same work over and over because no one knows who already knows something.
- People who want to get better at their jobs but don’t know what to learn
- Companies that make training choices based on guesses of real needs.
- Consultants who struggle to prove they are good, beyond a portfolio or a list of past clients.
None of these issues are new. People have tried to fix parts of this for years using resumes LinkedIn likes, certificates and performance software.. All of those solutions feel incomplete. They only show part of the picture. Don’t make it easy to use.
That was the gap I kept thinking about. The more I thought about it the more I saw that the tools people needed weren’t there the way I imagined. So I decided to create one.
What CapabiliSense Actually Is
At its core CapabiliSense is a capability intelligence platform. I want to be careful not to oversell it because I think overselling early-stage products is part of what erodes trust in this space. What I’m building, in terms is a system that helps individuals and organizations identify, understand, track and develop capabilities in a structured honest way.
Of relying purely on self-reported skills or one-off assessments CapabiliSense is designed around a few core ideas:
- Capability mapping. Breaking down vague notions like “leadership” or “data analysis” into specific observable components that can actually be assessed and developed.
- Continuous tracking. Treating capability as something that evolves over time not a label assigned once and forgotten.
- Context-aware insight. Recognizing that capability doesn’t exist in a vacuum; its shaped by the environment the tools and the type of work someone is doing.
- Actionable development paths. Turning identified gaps into next steps rather than leaving people with a report they don’t know what to do with.
- Honest representation. Avoiding scores or vanity metrics that make people feel good but don’t reflect reality.
I want to be transparent that this is still evolving. I’m not claiming CapabiliSense has solved capability measurement once and for all. What I am claiming is that I’ve built something that treats the problem with rigor and more respect for nuance than most of what I’ve seen out there and I’m committed to improving it based on real feedback, from real users.
Why I’m Building This in Public, on Medium
This brings me to the part of the question people often ask: why am I documenting this journey publicly on Medium instead of just building quietly and announcing a finished product later?
There are reasons for this.
First building in public keeps me accountable. When you write publicly about why you’re building something you are forced to clarify your thinking. It is much harder to hide behind plans when you know people are going to read your reasoning and ask questions about it. Writing this article for example made me face assumptions I hadn’t fully examined before.
Second Medium specifically has a culture that rewards long-form reasoning over hype. I didn’t want to build a landing page of marketing language and call it a day. I wanted a place where I could explain the “why” behind decisions, share mockups, admit mistakes and invite conversation. The readership of Medium tends to include people who actually care about the reasoning behind a product, not the pitch. That’s the kind of audience I want feedback from.
Third I’ve come to believe that great products are shaped much by the people who use them as by the person building them. By sharing my process I’m inviting users, potential collaborators and even skeptics to poke holes in my thinking early—when it’s still cheap to change direction. That’s a position than discovering flaws after launch when the cost of changing course is far higher.
Finally most importantly I think transparency builds trust in a category like this. Capability assessment touches something. People are trusting a system to reflect something about their skills and potential. I don’t think you earn that kind of trust with an announcement. You earn it by showing your work admitting uncertainty and being consistent, over time.
What’s Missing From Existing Tools
Before I started building CapabiliSense I took some time to look at what was out there in the capability and skills assessment world. I won’t name any products but I can talk about the patterns I saw across the whole category because those patterns shaped how I designed CapabiliSense.
- A lot of tools measure skills by themselves without showing how those skills actually show up in work.
- The assessments often feel like one-time snapshots of living profiles that grow over time.
- Results are usually numbers or badges with little guidance on what to do next.
- Self-assessment tools tend to be unreliable because people judge themselves based on confidence, not performance some overestimate others underestimate.
- Organizational tools often focus more on compliance and reporting than on growth.
- Few tools connect personal development with organizational capability planning in a way that helps both individuals and the company honestly.
These problems aren’t mistakes. They happen because designing a capability system is hard. It takes thinking about psychology, fairness, how to interpret data and long-term usability not just nice-looking interfaces. That’s why I believe it’s important to build something instead of rushing out a shallow version just to be first, to market.
The Principles Guiding How I’m Building CapabiliSense
Because flashy claims do not show why this project matters I will state plainly the principles that guide its development. These are not marketing slogans. They are the limits I set for myself.
- Honesty over flattery. The system must never exaggerate a persons capability just to make the experience feel nicer. A tool that only says what people want to hear is not useful.
- Clarity over complexity. Capability data can become very complicated quickly. I choose clear easy‑to‑understand outputs of impressive but confusing dashboards.
- Development over judgment. The goal is not to rank or label people for good. It is to show where a person stands now and what a sensible path forward looks like.
- Context matters. A capability score without context is almost meaningless. I build the system to consider role, environment and available resources of a one‑size‑fits‑all standard.
- Privacy by design. Capability data is sensitive. Users should always understand what is tracked why. Who can see it.
- Iteration over perfection. I would rather release something imperfect then improve it with real feedback than stay forever chasing an ideal version that never arrives.
I keep these principles in mind all the time when I make decisions especially when I want to take a shortcut that would make the product look more impressive in a demo but would be less honest, in practice.
Illustrative Scenarios: How CapabiliSense Could Change Everyday Situations
I want to be careful and open. CapabiliSense is still being built,. I do not yet have big proven case studies to show. Instead I can give example scenarios made up from patterns I have seen times that show the kind of problem I hope CapabiliSense will solve. Think of these as experiments in thought based on common situations not on recorded results.
Scenario one: The overlooked generalist. Picture someone who has a mix of skills: part project management, part technical troubleshooting, part client communication. On a resume each skill alone does not look very strong.. Together they make the person very good at handling complex cross‑team projects. A capability‑mapping method could show this mix clearly of making the person choose one label that hides the rest.
Scenario two: The team with expertise. Think of a team where one person quietly becomes the unofficial expert on an important internal process but no one writes it down. If that person leaves the knowledge leaves too. A continuous capability‑tracking system could warn about this concentration of expertise early so the team could record the process. Train others before it becomes a danger.
Scenario three: The professional stuck on a plateau. Imagine someone who has been “good enough” at their job for years. Cannot see what stops them from moving up. Vague comments like “work on your leadership” are not helpful. A clear capability breakdown that splits leadership into observable parts—such as making decisions when unsure, delegating or handling conflict—gives that person a real target to improve.
These scenarios are not real case studies. I want to say that clearly. They show the kinds of problems I see in talks in my work and in patterns I read about many times. I hope that as CapabiliSense grows I can share true confirmed stories from users with their permission and I am looking forward to that point. For now honesty about where this project’s matters more to me, than borrowing trust I have not earned.
The Hard Parts of Building This
I don’t want this article to sound like a highlight reel so I’ll be honest about the parts that have been genuinely tough.
- Avoiding oversimplification. has been hard. It’s easy to reduce capability to one number because numbers are simple to show and compare.. A single score usually hides more than it shows. I’ve had to fight that urge over and again.
- Balancing structure with flexibility. has also been challenging. Different industries and different jobs need ways of measuring capability. I wanted something structured enough to be practical. Flexible enough to work across many situations. That was one of the design decisions.
- Designing for trust. has been critical. Capability data is personal. Every choice in the design has to consider how it affects a person’s sense of fairness and safety. This isn’t something you can add after the fact—it needs to be built in from the start.
- Resisting the urge to over-promise. has been another struggle. Early on there’s pressure to make the product sound more powerful than it actually is. I’d rather say less than what we’ve achieved today and let the product grow into its potential over time.
I believe being open about these difficulties is part of what E-E-A-T-style credibility means. Not as a checklist. As a way of staying honest, about what’s hard what’s still unclear and what I’m still learning.
Who This Is Really For
CapabiliSense isn’t trying to serve everyone. Based on the challenges I’ve described here’s who I think will benefit most:
- People who want a more organized view of their own professional skills—not just vague self-assessment.
- Team. Managers who need a more accurate picture of team capabilities without relying only on gut feelings.
- HR. Learning-and-development professionals who want to connect capability gaps to real development plans.
- Independent workers who want a more credible way to show their skills to clients.
- Career changers who want to understand which of their abilities carry over to new fields and which ones they still need to build.
If you don’t fit neatly into any of these groups CapabiliSense might still help you.. These are the people I’m focusing on most closely when I design and build.
Where This Is Headed
I do not wish to make promises about the future because I believe that is the type of overreach I am trying to avoid in the project.. I can share the direction the project is currently moving toward.
In the term I am focused on refining the main capability-mapping engine and making sure the project produces results that feel genuinely accurate and useful to early users not just technically impressive. After that I want the project to build tools for teams and organizations to view combined, anonymous capability trends always with clear consent and transparency about what is being shared.
In the term I am interested in exploring how capability tracking could integrate with learning resources so that once the project identifies a gap the path, to closing it is not left entirely to the user to figure out alone.
None of this is locked in. Part of the reason I am sharing this journey publicly is so that the direction of the project can be shaped by conversations, not just my own assumptions sitting in a notebook somewhere.
What I’ve Learned So Far From Writing About This Publicly
Since I started talking about this journey some lessons have already become clear to me.
- People react a lot more to being honest about not knowing than to being sure about having the answer.
- Telling people the reason behind a choice creates more real connection than just saying a new thing is available.
- Readers can tell when something seems like advertising pretending to be thoughts and they stop paying attention when that happens.
- Being clear about what something can’t do makes people trust it more instead of less.
These lessons have changed the way I am writing this article, which’s why I have tried not to make big claims, about what CapabiliSense can do right now.
How I’m Thinking About Early Success
One question I get asked often is how I’ll know if CapabiliSense is actually working, in these early stages before there’s a large user base to draw conclusions from. I want to answer this rather than pointing to vanity metrics like sign-ups or page views because those numbers say very little about whether the core problem is actually being solved.
Instead here’s what I’m watching closely in the phase:
- Whether early users describe their own capabilities more specifically after using the platform than they could before even in casual conversation.
- Whether managers who try the team-level view say it changes how they think about development conversations, not how they run them administratively.
- Whether the feedback I receive challenges my assumptions than simply praising the concept since genuinely useful feedback is rarely just positive.
- Whether people come back to update their capability profile over time which would suggest the tool is being treated as a living resource than a one-time novelty.
None of these are the kind of metrics that make for a slide in a pitch deck and that’s somewhat intentional. I’d optimize for genuine usefulness in the early stages than for numbers that look good but don’t reflect whether the underlying problem is actually being solved.
I also want to be transparent that some of my assumptions will almost certainly turn out to be wrong. Maybe the way I’ve structured capability categories won’t map cleanly onto industries. Maybe the language I’ve used to describe development paths will feel too clinical, for some users. Not structured enough for others. Part of why I’m documenting this is so that when those adjustments happen they’re visible and explainable not quietly buried in a changelog nobody reads.
Why Capability Deserves This Level of Care
It is easy to treat this as another productivity tool something you try for a week and then forget.. Capability is closer to identity than most tools think. How a person understands their capability shapes confidence, career choices and even the view of their own growth potential. Getting that wrong with good intentions can cause real harm whether by reinforcing an inaccurate self‑image or by directing a person toward development areas that actually do not matter for their goals.
That is part of why I keep going to the principles I described earlier in this article. It would be far easier and probably faster to make a quiz‑style tool that produces a shareable badge and then stops. Many products in this field have taken that path. Some of them have achieved commercial success.. That approach does not honor what capability really means to the people being assessed and I am not interested in building something that I would not trust with my own career decisions.
This also explains why I keep returning to context often. Two people with scores on a given capability dimension can be in completely different situations. One may be early in their career, with growth potential while the other may already be operating near the maximum that that particular skill usually requires in their role. Treating those two situations the same would be misleading even if the number itself is the same. Building a system enough to show that difference without becoming so complex that it is unusable is one of the challenges I expect to keep refining for a long time.
Final Thoughts
Building CapabiliSense began with an observation: capability is one of the most important parts of a persons professional life. Yet we measure capability poorly we talk about capability poorly. We grow capability inconsistently.
That gap felt worth fixing. We did not want to add another quiz. Instead we wanted a thoughtful system. The system is built on honesty on context and on development not on static labels.
Sharing this journey, on Medium is not a marketing strategy. It is a promise to build something you can trust. I would rather show you the reasoning, the uncertainty and the process. I do not want to hand you a pitch and ask you to take it on faith.
If you have read this far thank you for spending time to understand not what I am building but also why. I will keep writing about this process as it unfolds. I will also write about the parts that do not go as planned.
Frequently Asked Questions
What exactly is CapabiliSense?
CapabiliSense is a capability intelligence platform. It helps people and organizations find, track and grow capabilities in a clear, honest and context-aware way. Of relying on fuzzy self-assessment or fixed labels it offers a structured approach to understanding what someone can actually do.
Why are you building CapabiliSense specifically?
I kept running into the problem from many different angles. People had trouble describing their skills. Managers couldn’t see capability across their teams clearly.. Existing tools offered only partial or shallow solutions. That’s why I built CapabiliSense. To fill that gap properly.
Why did you choose to document this journey on Medium?
Medium encourages long-form writing. It’s not about hype or quick wins. That kind of environment matches how I want to share this project. Writing publicly also keeps me honest. It holds me accountable. Lets me get early feedback while the direction is still open.
Is CapabiliSense finished or still in development?
It’s still being built. I’m making sure not to overpromise what it can do today. I’m being transparent that features, frameworks and design choices are still evolving. Everything is shaped by feedback.
Who is CapabiliSense designed for?
It’s made for individuals who want clarity on their capabilities. For managers who need a truthful view of team strength. For HR and learning professionals creating development plans. For freelancers wanting to show expertise.. For anyone changing careers trying to understand transferable skills.
Does CapabiliSense replace performance reviews or resumes?
No. It doesn’t replace them. It works alongside processes like performance reviews and resumes. Its goal is to give a more continuous and nuanced picture of capability. It adds depth without replacing structure.
How is capability actually measured in CapabiliSense?
The system breaks down skills into smaller observable parts. It tracks those components over time with attention to real-world context. There’s no score. Instead it focuses on insight. Not oversimplified ratings.
Will you share real case studies from users in the future?
Yes I will.. Only when there are verified stories, with user consent. Now I use illustrative examples, not real data. That matters. Because honesty and trust are important.
How can I follow the progress of CapabiliSense?
The best way is to keep reading this series on Medium. I plan to share updates, design decisions, challenges and lessons learned as the project moves forward.
