Question 1

How do you know a brand system will hold?

Accepted Answer

Let them make something real, then look at what they produced. Not at whether they liked the guidelines. If the result belongs in the system without a round of corrections, it holds. Every correction you have to make is a rule that exists in your head and nowhere else.

Question 2

Why does internal software fail on adoption?

Accepted Answer

People read effort as a signal of whether something is supported. A tool with inconsistent spacing, three shades of grey and a settings page that was clearly built last says: this will break and nobody will fix it. So they keep the spreadsheet.

Question 3

Where should a design system live?

Accepted Answer

Put it where people already are. Logos, colours, templates and signatures inside the tool they open every morning, one click from where they work. Then the question "which logo do I use" stops being a question.

Question 4

Who should train an internal AI system?

Accepted Answer

An outside consultant needs three months to learn which folder is real and where the exceptions live, and still gets it wrong, because what they are told in workshops is how the process is supposed to work, not how it runs.

Question 5

Is it cheaper to migrate later?

Accepted Answer

Better tools do arrive every year. So does another year of data in the old system, another set of processes built around its limitations, and another cohort of people who only know how to work that way. The migration does not get easier as it gets later. It gets heavier.

Question 6

Why does software spend keep growing?

Accepted Answer

Because nothing ever leaves. Each tool arrives to fix a symptom the last one produced, and it arrives carrying its own version of a process nobody wrote down. Two years later three systems hold three versions of the same workflow, and the fourth purchase is the one meant to reconcile them.

Question 7

What should the first internal tool solve?

Accepted Answer

Start with something small that annoys everybody equally. Where the logo files live. Which meeting room is free. Who has the current version of the deck.

Question 8

What does vendor software actually cost?

Accepted Answer

Count the waiting rather than the invoice. How many changes did you request last year, and what was the average time from asking to having them? Multiply by the cost of the people who waited.

Question 9

What can a vendor not do for you?

Accepted Answer

What gets described in requirements sessions is how the process is supposed to run. What gets built is that description. The gap between the description and the reality is where adoption dies.

Question 10

How do you know a process is ready for software?

Accepted Answer

If nobody can write it down in one page, you do not have a process. You have a set of habits that happen to produce an outcome most of the time, held together by two people who know the exceptions. Software will not fix that. It will encode it, and then the exceptions become bugs.