Atlas · Audience
Product Managers
The person logging in is not always the customer.
Login proves who is at the screen. It does not prove what they own, may manage, or can buy. Model those questions separately before the edge cases arrive.
My AI was smart. It just couldn't see my job.
My work context was scattered across email, meetings, documents, and notes. So I wired it into a private Obsidian vault Claude Code can read.
Multi-market apps: the central vs. local paradox
How to run a multi-market app with one shared codebase, local deployments, clear decision rights, and room for real market differences.
The app consolidation playbook
Large app portfolios grow through local decisions, acquisitions, and separate teams. Consolidation works when one owner can remove duplication while keeping the local differences customers need.
Build the API layer before replacing the billing system.
Do not make digital delivery wait for a full OSS/BSS transformation. Put a stable API contract between new demand and the legacy systems already running.
The laundry list trap: why much of your roadmap doesn't matter
We analyzed engagement across an entire app feature set. Over 40% of the candidate scope generated less than 2% of measured engagement. I use that evidence to decide what deserves a place on the roadmap.
Your telco app should be more than a service channel.
I watched European telco apps move from self-service into sales and retention. These three phases explain what changed and where the programs became stuck.
Claude Code and the context window on bigger projects
My website is close to a thousand files. I keep Claude Code useful by giving each session one task, naming the files involved, and keeping the project instructions current.
Claude Code permissions: what to allow and what to block
Claude Code can change real files and run commands. Check the permission mode, protect secrets, review the diff, test the result, and keep a restore path.
What is vibe coding, and when should you use it?
Vibe coding is useful for disposable experiments where failure is cheap. Software you intend to keep needs review, tests, version control, and an owner.
Keeping your Claude Code project organized
Give each file an obvious home, document the stable rules, and test what your deployment actually includes.
Teaching Claude Code your standards with rule files
Use CLAUDE.md for project-wide facts and rule files for detailed standards, including rules that load only for matching paths.
Creating reusable Claude Code skills
If you keep pasting the same prompt, save it as a small Claude Code skill. You can run it with a short command and add templates or scripts later.
The CLAUDE.md file: what to put in it, and what to leave out.
Each Claude Code session starts with fresh context. CLAUDE.md loads the project facts and instructions you want available, while auto memory stores patterns Claude learns.
Stop trying to digitalize everything
Do not delay a clean common journey while reproducing every legacy exception. Start with measured demand, keep a human handoff, and add the next case only when it earns its place.
Your digital team needs to act like a startup
A digital team does not become startup-like through a new workspace or delivery process. It needs clear authority to decide, say no, and change course when evidence changes.
Why renaming IT to product didn't fix anything
Renaming an IT team to Product changes nothing if the same people still decide what gets built. Follow the decisions, measures, funding, and incentives instead of the org chart.
When Claude Code goes wrong (and it will)
Claude Code will sometimes make the wrong change. Inspect the diff, use checkpoints for session recovery, and keep Git for a durable restore point.
Set up Claude Code so you can review changes as they happen
Keep Claude Code and the result visible at the same time so you can review each change before asking for the next one.
Asking Claude Code to do multiple things at once
Claude Code can delegate independent parts of a task to subagents. Use parallel work for separate research or checks, then review one combined result before editing.
Giving Claude Code better instructions
Give Claude Code the problem, relevant context, and the result you expect. A specific instruction reduces guessing, but you still need to review the result.
How Claude Code sees your files
The folder where you start Claude Code is its main working directory. Keep one project in scope, then add other directories only when the task needs them.
Your first conversation with Claude Code
Create a separate practice folder, then use three prompts to inspect it, create a file, and edit that file while reviewing each action.
Installing Claude Code without the old Node.js setup
Install Claude Code with Anthropic's current native installer on Windows, macOS, or Linux. No Node.js, no npm, and the fixes for when the command is not found.
Opening the terminal for the first time
You need four terminal actions to start Claude Code: open it, run a command, move to the project folder, and close it when you are done.
Meet your AI assistant that actually does things
Claude Code can inspect a project, use development tools, and apply approved changes. Your job is to decide what should happen and check the result.
Digital transformation reality check
The programmes I have seen stall did not stall on technology. They stalled on who was allowed to say no, on roadmaps nobody had pruned, and on systems everyone agreed to replace and nobody could afford to. Eight pieces on what actually moves: how a digital team has to be set up before it can ship anything, how to decide what is worth digitalising at all, and what to do about the systems you are stuck with. Each one comes out of work I did, not out of a framework. Read it front to back for the argument, or take any piece on its own.
How to use Claude Code
Claude Code is Claude working inside a folder on your computer. It reads your files, edits them, and runs commands, and you tell it what you want in plain English. No code to write, and no development background needed to start. Twenty-four short chapters, in five modules, take you from opening a terminal for the first time to a website that is actually live. After that, the habits that keep it useful once the project outgrows a handful of files. Start with the overview, which is the whole loop on one page. From there the chapters stand on their own, so you can read in order or open the part you need.