The first two weeks decide the year.

Two pilots launch on the same morning. Same tool, similar budget, almost identical launch announcements. Fourteen days later, the first has become a morning habit for a third of the employees; the second is a link hanging in an unopened email. Six months later the first will be written up as a success story and the second as lessons learned — but both stories were actually written in the first two weeks.

In the closing reviews someone will say the difference was culture, or leadership enthusiasm, or a feature missing here and present there. All of that describes the smoke. The fire caught or died very early, when everything real was being decided in a handful of days: who gets in, how they get in, what they find waiting once inside, and what they are told — honestly — about what gets recorded.

A pilot does not die in its sixth month. It stops breathing in its first week, and the announcement runs late.

Identity before features

The pilots that survive share one first decision: they start from identity, not features. The employee does not register for a new tool; they open a gate that already knows them, with the same work account that opened their email that morning. No new password to invent, no invitation waiting in an inbox, no page saying create your account — the sentence that has ended more pilots than tight budgets ever did.

Every registration step is a tax paid out of the employees’ stock of curiosity, and that stock is not replenished by a second circular. This is why the enterprise adoption path begins with what we call the identity week: before any talk of use cases, single sign-on has already made the gate a natural extension of the office, not a strange website asking for paperwork.

Identity has a second, quieter effect: when everyone enters through one door, no manual accounts sprout at the margins, and no spreadsheet tries to remember who joined and who left. A pilot that begins with a small mess of accounts is promising a large mess at scale — and scale is the exam the whole year is graded on.

On by default, not on request

The first question an employee asks any new internal assistant is not what can you do? but what do you know? If the answer is nothing, until someone opens a permission for you, the tab is closed politely and never opened again. Surviving pilots switch the safe sources on by default from the first hour: the published employee handbook, the recurring HR questions, the public policies — everything no one disputes showing to any employee.

Safe here is a decision the organization makes, not a vague adjective: sources already public to all employees open to everyone, while sensitive sources stay behind a clear permission request that passes through a named approval. The employee finds usefulness in the first minute, and the organization finds its boundaries intact in the same minute.

And the balance is shown from day one, not after the first financial surprise. When an employee watches their own small number move with every request, they understand the rules of the game without a circular: experimenting is allowed, the cost is visible, and neither they nor their manager will be ambushed. The anxiety of how much will this cost? extinguishes more curiosity than any ban ever has.

The difference between launch methods is not an organizational taste; it shows up as a number in week two. This is what the picture looks like, in illustrative figures and nothing more:

The moment of candor

In that same first week falls the moment that fixes the employees’ relationship with the whole system. We call it the moment of candor: the sentence said in full and without cosmetics — there is a register; it binds decisions and declared metadata, not your thoughts; and it is shown to you exactly as it is shown to management. Whoever reads their own register invents no legend about it, and whoever understands the rule plays inside it at ease.

Pilots that postpone this sentence pay for it twice over: employees discover the register through corridor rumor, it turns in their minds from a rulebook into a trap, and usage migrates to where there is no register at all. That is why the employee enablement playbook places this moment on day three at the latest — before the corridors speak on your behalf.

And the moment is not a speech given once and forgotten; it is a line the employee sees inside the interface itself whenever they ask: what was recorded about me today? The answer appears to them first. Candor that lives in the product is believed; candor that lives in slide decks is forgotten with the last slide.

The manager is a partner in the same moment: they see their team’s balance and decisions with the same clarity, so they are never forced to choose between blind trust and crude surveillance. Mutual candor in week one costs far less than a forced reckoning in month four.

None of the above needs an exceptional budget or technical heroics. A connected identity, safe sources open by default, a visible number for every employee, and one honest sentence said early: four decisions taken before launch and executed in days — yet they separate a pilot that becomes a habit from a pilot that becomes a slide deck about why things stalled.

What an employee touches in their first week is what they will believe about the system for the rest of the year.

The first two weeks do not predict the year; they manufacture it. Everything after them is an echo — it carries far if the voice starts clear, and it dies out if the voice starts as a murmur behind a closed door. So when you ask yourself when the governance of a whole year begins, the honest answer is: before its third week.