Nufar Gaspar

So that will be the identity.

And here's the key to actually building a good identity file.

You don't write the file from scratch yourself.

You will hate it and you will quit.

Instead, I encourage you to brain dump to an AI and let the AI interview you.

So open any AI tool and ideally one that already has sufficient memory of you from ongoing work with you and say,

I'm building my identity file.

Please ask me 15 questions about how I work, what I want, what I don't want, what frustrates me about AI today, and what rules I want enforced.

You answer, and ideally out loud because it's much easier to speak to an AI tool.

And then the AI will draft, you will edit, and you will shift a first version that, let's say, is about 70% right.

You can patch it over the next three weeks as you notice the gaps.

And basically, this is the methodology for every layer that we will cover today.

You brain dump, you let the AI interview you, you draft, you shift a minimal viable version of this file, and then you improve.

And for our chief of staff, identity will capture your communication style, your pet peeves, your non-negotiables.

For example, never let me walk into a meeting without a pre-read or always tell me who else I owe to reply to or flag when I'm over committing for the next week.

And then we have the context.

The context is what you know.

And what you know is the single biggest predictor of whether AI gives you the generic output or something genuinely useful for your actual situation.

So generic AI advice is just like one Google search away.

And what you cannot get from the public internet is your situation, your roadmap, your org chart, your customer segments, your priorities, and so on.