Our team recently sat down and started talking about some trends we think might pick up steam for 2016. The conversation ventured down another road, trends we wish would go away. While I would necessarily call these trends, this article points out a lot of nuisances that sites still make us go through, and we still deal with on a day-to-day basis. WHY!?! Make it stop!

A lot has happened this year, for all of us in this world. This year, we decided instead of just focusing on us, we would take this time to reflect on our year by also highlighting charities that we support. We invite you to read about our reflections on 2015, our hopes for 2016, and the charities we care about.

The folks over at PSD to WordPress reached out to ask about thoughts on CSS frameworks. Brian had a few words to share to their roundup.

A few weeks back I saw this article from Jared Spool in my twitter feed - and the timing was eerily perfect. We were in the midst of re-examining what it was we were doing for our client and why. The roadmap we had originally created had shifted and morphed and when all was said and done, there we were with a "map" but the idea of where we were going, our focus, got hazy. To most, it just looked like a bunch of feature changes.

Building a roadmap is challenging. You know the least amount you will know at the beginning, and that is when your team (and your client) want to know what it is you plan to do and how much will it take. Historically, we've tried different approaches to make this more efficient and realistic for us and our clients. But at the end of the day, roadmaps tend to just look like a big list of features, a bunch of "stuff" that we are going to do. In the background, it's all intentional and tied to the needs we've so far determined, but it doesn't make the picture clearer. The idea of identifying the themes to focus our discussion and solutions is one I'm willing to try. It may not be the only answer for roadmaps and project scope, but if anything - it's the place to start.