Approach
Let's understand the work, then make it easier.
I start by listening to how things happen today: what works, what you've already tried, and where you keep having to step in.
From there, we can work out what would help. Sometimes that's a simple automation. Sometimes it's a web app, a clearer handoff, or a connection between tools you already use.
About Pat
I'm Pat Morrison, an independent builder of operational systems. When we work together, you're talking directly with the person building the solution.
I didn't start building software to become a software developer. I started because I've seen how much time and energy is lost when information doesn't move where it needs to go.
I like figuring out how things workâand helping them work better. I use many of the tools I build myself, so I experience the awkward steps and missed notifications firsthand.
My questions tend to be practical: How does an update get from the field to the office? Who needs to act on it? Can they find what they need? How do we know it was handled?
A place for information, a next step for work.
Getting Things Done has influenced my approach. This is the loop I use to think through a workflow:
- Capture. Bring information in through a channel people can use: a text, a voice message, a photo, an email, or a form.
- Clarify. Work out what it means and what should happen next. Flag the decisions that need a person.
- Dispatch. Get it to the right person, project, or tool.
- Act. Keep the relevant information with the work.
- Review. See what's moving, what's waiting, and what needs attention.
The goal is a shared picture of the work. Each person should be able to find what they need and see what needs their attention, even when the information comes from different tools.
I use what I build.
- Voice assistant. Live, personally used Takes my calls and messages, transcribes them, and sends them to Discord so I can follow up.
- Business email alerts. Live, personally used Brings new business emails to my attention in Discord instead of leaving them buried in my inbox. I still read and reply to the original email.
- Carryall. Personally used Helps me capture information, organize next actions, and review my own work. Using it myself gives me a place to test and refine the approach.
Those experiences inform how I build for others: understand the problem, make a useful change, and keep learning from the people using it.