Just recently, the Michigan Secretary of State faced a big problem. Their digital system stopped working. They had spent too many years updating an old system, trying to make incremental fixes here and there. They didn’t have a plan in place for the software retirement, so before a new solution could be enacted, they faced a total breakdown. Therein lies the danger of ignoring technical debt.
I couldn’t talk about any project management tool, without first talking about the people behind it. I have the distinct pleasure of leading Springthrough’s talented group of project managers. We’re more than task and budget managers. While time, cost and profile are important; we value the human element. To meet each client’s unique personal and business needs, we actively adapt our approach to each project.
Since I started at Springthrough a little more than a year ago, the firm’s website has been a topic of discussion. My suspicion is that even before I began, people were tossing around the idea of a new site. It seems pretty common to be most critical of your own website.
It’s not uncommon for a client to request a custom integration between their existing software and any new systems they plan to implement. I’ve seen (and built) integrations with SAP, Salesforce, legacy applications, and many others. In the case of website development (something we do frequently at Springthrough), connecting a content management system with other platforms can take a website from a marketing brochure to an actual tool.
We talk a lot about our process — Insight, Clarity, and Enablement — and how that translates into activities and deliverables. But as this process becomes more and more ingrained within our culture, it's obvious that it is bigger than simply a checklist of activities.