Writing
Things I’m thinking about.
- When the AI is wrong, who signs for it?AI produces answers quickly, but a person still owns the outcome. Who reviews AI output, who is accountable, and where AI should not decide alone.
- Doing business across the GCC: what changes at the borderExpanding technology services across GCC markets is not copy and paste. What changes between countries in contracts, tax, billing, delivery and expectations.
- Busy isn’t the same as movingA team can be fully occupied and still make no progress. How to tell activity from movement, and the small changes that get work moving again.
- Why the cheaper proposal usually costs more in year twoCost rarely disappears in a vendor comparison. It moves into your team, your support model and your renewal. A simple way to compare three years honestly.
- Cloud credits are not a strategyCloud credits make the first year cheap and the second year a surprise. What credits really pay for, what they hide, and how to plan for the day they end.
- The contract is the architecture document nobody readsThe signed agreement decides more about a technology project than the design does. Why delivery teams should read it first, and what to look for.
- Most DR plans are tested against the wrong failureDisaster recovery tests usually prove that servers come back. Real outages are messier. How to test DR against the failures that actually stop a business.
- Meetings happen. Decisions stay open.Many meetings end with discussion and no decision. A simple routine to close decisions in the room, record them and stop the same topic coming back next week.