As of August 24th 2019, Drupal 6 has been in Long-Term Support (LTS) for 3.5 years. That’s right, three and a half YEARS years since Drupal 6 End-of-Life (EOL), and we’re still talking about it.

If you’re here you might be asking yourself:

I’m proud to say that we’re one of the few consultancies to provide Revenue Share agreements across marketing and sales campaigns with our clients. In an agency world of Pay Per Lead (PPL) and payment based on a percentage of Paid Advertising Budget, we’ve succeeded in often negotiating and aligning interests with our customers and partners around mutually beneficial outcomes. 

I’m equally ashamed to say that we’ve had more than our fair share of poor investments. Poor investments in companies, clients, and partners that we failed to properly assess and set up for success. 

Scaling our hiring pipeline as a core team of 2 consultant-owners has had it’s challenges. We went through the transition from go-with-your-gut hiring to a repeated-and-true hiring practice a few years ago. The critical learning for us was the data. We needed to ask all hires the same questions so we could learn about who they were without getting bogged down managing our talent pipeline. 

Digital Transformation is often written about for its impact on an organization. Especially in higher education, there is a monumental effort placed by many teams across multiple departments to evolve digital systems and best practices. The goal for any institution is always simple in nature: deliver on technology’s original promise—to get a multiple of work done with fewer resources. We often dress up this promise to be more complicated in our efforts to coordinate, project confidence, and (sometimes) coerce others to get in line with this transformation. 

The city of the future will not be defined by success or growth while resources are abundant, but instead will be defined by the way intelligent, risk-mitigating decisions are made to maximize delivery of critical city services.

To make intelligent decisions about complex City systems and services, you need data. And not just census data or statistics. You need the inner workings of the city’s operations. The metadata and messy, non-normalized data from all of your various applications, services, and systems.