Start product recommendations with rules, not AI.
Start product recommendations with your best sellers and clear rules. Separate customer and product eligibility from ranking before adding an AI model.
Pricing rules when a guest becomes a known customer
Decide what happens to a selected offer after login reveals the customer's eligibility. Explain any price change and preserve the accepted offer through checkout and billing.
A checkout countdown has to earn its delivery promise.
A checkout countdown can create urgency or support a real delivery promise. That promise needs clear rules for what changes at zero, which date to show, and how it survives payment.
Customer accounts: separating users, owners and permissions
A person may manage a service they don't own or place an order for a company. Keep the user, customer, permissions and order context separate.
What using Claude Code actually looks like
Using Claude Code is a loop: ask, change, check, decide. Here is what a normal session looks like, six commands worth learning first, and how to recover when it goes wrong.
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: what central and local teams should own
How to run a multi-market app with one shared codebase, local deployments, clear decision rights, and room for real market differences.
Choosing what to build when AI makes prototyping cheaper
AI can make execution cheaper, but it also exposes weak decisions faster. The valuable skill is defining work clearly enough to test whether it matters.
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.
How we used feature data to cut a telco app's scope
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.
Telco apps: from self-service to sales and retention
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.
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.
Choosing which customer journeys to digitalize first
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.
Which decisions should your digital team own?
A digital team needs authority to decide, say no, and change course when evidence changes. Agree on risk limits and escalation points before delegating those decisions.
Moving from IT delivery to product ownership
Follow one product decision from customer problem to release. Check who chooses the work, who can reject a request, and who owns the result.
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.
What Claude Code can do with your project
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.
Build an AI work memory with Obsidian and Claude Code
Collect email, calendar entries and work documents in an Obsidian vault Claude Code can read. The published chapters cover the system overview, Outlook capture with Power Automate, processing with scripts and AI, and daily commands. Start with the overview or choose the part you need. The local meeting transcription chapter is still coming soon. Route map connecting the five parts of the AI work memory guide to one plain-text hub: connected work context, email and calendar capture, local meeting transcription, script-first processing, and daily commands The numbers match the guide order, but this is a map rather than a dependency chain. Start with the overview for the whole system, follow the route, or open the capture, transcription, processing, or daily-command part on its own.
Digital transformation: teams, priorities and legacy systems
Eight articles on decisions that shape digital transformation: who owns the product, which journeys and features deserve investment, and how to work with legacy systems and multiple markets. Read the guide in order for the full argument, or choose the decision you are working through now.
How to use Claude Code
Learn to use Claude Code by building a personal website, from opening the terminal and installing it to reviewing changes and putting the site online. The guide has 25 chapters in five modules. Start with the overview for the whole workflow, follow the chapters in order, or open the part you need. Later chapters cover project instructions, reusable skills, permissions and working with larger projects.
Confluence
Team wiki and documentation from Atlassian.
Google Analytics
Web and product analytics at scale.
Jira
Issue tracking and agile project management.
Plaud
AI voice recorder that turns meetings into transcripts, summaries, and action items
Figma
Collaborative interface design and prototyping.
Obsidian
Local-first markdown knowledge base.
Microsoft Teams
Chat, meetings, and collaboration in Microsoft 365.
Slack
Channel-based messaging for teams.
Google Workspace
Gmail, Calendar, Docs, Drive in one suite.
Backlog.md
Markdown task tracker that lives in your git repo