Hello, I’m JP.
J-P. Like the bank. Except I deal in ideas, not money. 😂
I’ve spent more than 20 years working across business transformation, enterprise architecture, ERP, CRM, and technology solutions.
Much of that time has been spent helping large organizations understand complicated problems and figure out how to solve them.
And there’s one question I still find myself asking.
Why are we doing it this way?
Sometimes the answer makes perfect sense.
Sometimes the answer is “because that’s how we’ve always done it.”
Those are usually the conversations I enjoy most.
How I think about technology.
I like technology. I like AI. I like building things.
But I don’t believe every problem needs a new system, a complicated architecture, or an AI agent.
Sometimes the best solution is surprisingly ordinary. Other times, a new technology makes something possible that wasn’t practical before. The interesting part is knowing the difference.
That’s what architecture means to me. Not drawing impressive diagrams. Making good decisions about how things should work.
Why this website exists.
I’ve learned a lot from people who were generous enough to share what they knew. Colleagues. Engineers. Architects. Business leaders. People who challenged my assumptions. People who told me an idea wouldn’t work.
And occasionally, people who were right. 😂
Now I’d like to share more of what I’ve learned and what I’m still figuring out. Especially with people who want to become Business AI Architects, build their own consulting practices, or help businesses solve problems using better systems.
Not because I have all the answers. I don’t. But I have some methods, tools, experiences, and ideas that might save someone a few years of trial and error.
Or inspire them to build something I never thought of. That would be pretty interesting.
What I’m exploring today.
My work continues to focus on Business AI Architecture and the AI-DLC: designing systems AI can work inside, and building them from canvas to customer with people firmly in the lead.
I’m particularly interested in making these capabilities more accessible to independent professionals and smaller consulting firms.
Because I don’t think good engineering should be reserved for organizations with enormous budgets.
A few things I believe
A few things I believe
- Start with the problem.Technology comes later.
- Question inherited conclusions.Respect expertise. But don’t confuse experience with proof that something can’t be done differently.
- Engineer before you automate.A broken process running faster is still a broken process.
- Use AI where it makes sense.And be perfectly comfortable not using it when it doesn’t.
- Build something.Ideas become much more interesting when they meet reality.
- Share what you learn.Someone else might take it further than you imagined.
Let’s compare notes.
If you’re building something interesting, exploring Business AI Architecture, starting a consulting practice, or questioning how a business process works, I’d enjoy hearing about it.
No elaborate pitch required. Tell me what you’re working on. Or what you’re trying to figure out. Maybe we’ll learn something from each other.
— JP