The client's real problem is never the one in the brief. It's always three conversations deep. Lessons from years of consulting that nobody puts in the textbooks.
Things architecture school* doesn't teach you:
(software architecture, not buildings — though honestly both apply)
011. The Client's Real Problem Is Never the One in the Brief
It's always three conversations deep. You have to earn the real brief.
The first conversation is what they think they want. The second conversation is what they actually need. The third conversation — if you've built enough trust — is why they need it, which is usually a political or organizational problem wearing a technical costume.
022. "Just a Quick Question" Is Never Quick
It's a 3-week engagement wearing a trenchcoat.
Learn to scope aggressively. "Quick questions" that turn into large projects aren't the client's fault — they're yours, for not setting boundaries early. At Apptivity, we've learned to say: "That's a great question. Let me scope what answering it properly would take."
033. The Best Architecture Is the One You Can Explain to a Non-Technical CEO in 60 Seconds
If you can't, it's too complicated.
This isn't dumbing it down — it's proof that you understand it deeply enough to simplify. The architects who hide behind jargon are usually the ones with the most brittle designs.
044. Underpromise. Overdeliver. Every. Single. Time.
This is the entire secret to repeat clients at Apptivity. Sorry for spoiling the mystery.
The temptation to oversell is enormous, especially when competing for contracts. But the math always works out: one honest engagement that exceeds expectations is worth ten oversold projects that disappoint.
055. Eat Lunch
Seriously. The code will still be broken after your sandwich.
I built Apptivity on these principles — not on having the fanciest tech stack. The fanciest tech stack is whichever one ships on time and under budget.