Systems over heroics

Early in my career, the whole operation could live in my head and on my phone. Which suites were vacant, which furnace was acting up, who promised what to whom. You can hold a small portfolio together that way, on effort and memory. But effort does not scale, and memory does not either. Today we run sixteen-plus buildings across five Alberta cities, and the honest reason that works is that we stopped relying on heroics and started building systems.

The question I ask about every part of the business is simple. What happens if this person is away tomorrow? If the answer is that everything stops, that is not a people problem. That is a missing system. A building should never depend on one set of hands, including mine.

Take our 24-hour maintenance response. That is not a promise held up by one manager answering calls at midnight. It is a process. A request comes in through one place, the whole team sees it, someone picks it up, and the clock starts. When the work is done, the ticket closes and the resident hears about it. Build that once and it shows up for every resident, in every building, every day, whether or not anyone is having a heroic week.

The same goes for follow-through. My rule is blunt: if it is not in the calendar, it is not happening. When I tell a resident I will get back to them in 24 hours, that call goes into the calendar before I hang up. Follow-through that depends on remembering is not follow-through. It is luck.

Systems are also how a standard travels. I want a resident in Stony Plain to get the same experience as a resident in Edmonton. So inspections run on a schedule, not on inspiration. Signage and community boards look the same from one building to the next. When every site runs the same playbook, quality stops being a matter of which manager you happened to get.

This thinking is why I helped build Rentdigi. Years ago my phone would not stop ringing. Applications arrived as email attachments. Maintenance lived on paper. There was no record of what had already been fixed in a suite. I went looking for software that did the whole job and found that every company had a piece of the answer, never the whole package, usually at a price built for much bigger operators. So we built one platform: applications, maintenance requests, the history of every suite, all in one place. Now when the same plumbing issue shows up twice, the record shows it, and we fix the cause instead of paying for the symptom again.

None of this is glamorous. A calendar entry, a checklist, a ticket that closes. But systems are how you keep promises at scale, and keeping promises is the whole business. Save the heroics for the days that truly need them. Most days should not.