Useful EA is built and operated by CTO Resources LLC, a Washington State company founded by Avinash Nicklas Malik — known professionally as Nick Malik.
About Nick Malik
Nick has spent roughly four decades in high tech, working across product development, internal software development, management consulting, and enterprise and business architecture — in industries ranging from hospitality and health care to insurance, financial services, and technology itself. His roles have included Principal Enterprise Architect at Microsoft and enterprise architecture leadership at companies including PitchBook, Infosys, Sierra Systems Group, and fine.com International, along with independent and fractional CTO work for smaller organizations.
He is a recognized voice in the Enterprise and Business Architecture community: a contributor to the Federation of Enterprise Architecture Professional Organizations (FEAPO), the author behind the long-running "Inside Architecture" blog, and a developer of practical EA methods including the Enterprise Business Motivation Model and the Minimum Sufficient Business Integration approach. He is a co-author of "Stories That Move Mountains" and a frequent conference speaker on the subject of turning strategy into work people can actually act on — the same problem Useful EA's tools are built to solve.
Nick lives in the Seattle area. You can find more of his background, writing, and speaking history on his LinkedIn profile.
Why Useful EA Exists
When I was a consultant, I'd sit down on day-one of an enterprise architecture engagement and ask: "Do you have an EA suite?"
My second question was: "Do you use it?"
Those are very different questions. I sometimes got one "yes." I never got two.
More than a decade ago, I helped champion the adoption of an enterprise-architecture tool at my employer. It cost more than $50,000 to bring in, even then. We spent nearly two years implementing it.
The tool was sophisticated. Its data was well organized. Its interface was solid. It did what it was designed to do.
Almost no one used it.
The problem wasn't the software. We had purchased a tool designed for a highly mature architecture practice before we had developed the processes, habits and governance needed to sustain one.
The license cost was only the visible cost. The larger cost was the organizational effort required to collect the data, keep it current, fit the tool into everyone's work and consistently turn that data into decisions people valued. That level of software sophistication required real effort and organizational buy-in.
We simply weren't ready to extract enough value from that level of investment.
Large EA suites have their place. A mature architecture organization with established governance, reliable data stewardship and broad participation can benefit enormously from them.
But many organizations aren't there yet.
Today, AI makes a different model possible: smaller, lighter and less expensive tools, each designed to solve one practical architecture problem well.
You don't always need the entire platform.
Sometimes you need to turn a capability spreadsheet into a usable model. Find the maturity gaps that matter. Trace a proposed investment back to strategy. Understand an application portfolio. Produce something useful for the next decision.
That is why I'm building Useful EA.
I'm not leading a revolt against sophisticated EA suites. I'm challenging the assumption that every architecture team must begin with one. I'm not selling to an enterprise. I'm pricing it for the individual architects. After all, if a carpenter can afford his own tools, why shouldn't the architect?
Start with the work. Use the tool that helps. Add sophistication when the practice is ready for it.
If your architecture team is still trying to create useful results with spreadsheets and slides, I'd like you to try Useful EA. Then after you do, tell me what would make it more useful to you.