My approach
Understand the work first. Then make the system simpler, stronger, and easier to run.
Start with the work, not the tool
Most technology frustration is not really a software problem. It is a process that lives in people's heads, a handoff nobody owns, or a set of exceptions that became the system. Buying another tool can hide that for a while. It rarely fixes it.
My approach is to make the work visible first. Once the process is clear, automation becomes safer, AI becomes more useful, and the technology choices get much easier to defend.
Principles I work by
Notice the real work
Watch how people actually get things done, including the workarounds. The workaround usually points at the missing system.
Define before automating
A vague process automated at speed is still vague. Name the steps, owners, inputs, outputs, and exceptions first.
Automate carefully
Automate repetition, routing, reminders, and data movement. Keep human judgment where the cost of being wrong is real.
Use AI as leverage
AI is strongest when it helps people draft, classify, summarize, decide, and move faster inside a clear process.
Build systems people can run
A system is not finished when it works once. It is finished when a team can understand, maintain, and improve it.
Keep the human path clear
Technology should reduce confusion. If people cannot tell what happens next, the system is not done yet.
A practical sequence
- Map the current process and the pain points people feel every week.
- Separate judgment work from repeatable work.
- Simplify the process before choosing tools.
- Prototype automation or AI assistance against real examples.
- Measure whether the work got easier, faster, clearer, or safer.
- Turn what works into a system the team can own.
That sequence is how I think about internal platforms, publishing workflows, website systems, and community ventures. The domain changes. The discipline does not.
What I do not lead with
- AI hype without a process to improve.
- Tool selection before the problem is clear.
- Automation that hides bad handoffs instead of fixing them.
- Systems only one person can operate.
- Complexity that makes the team slower in the name of sophistication.
Start a conversation
The fastest path is a short email. Say what you are trying to improve, where the process feels stuck, or what you want to build. Maple Peaks will reply from there.