What can’t be measured can’t be managed. Now, you don't need to be a data scientist to make decisions based on your users’ activity, but it’s crucial that your configuration is top-notch. As they say, garbage in, garbage out. Google Analytics provides an easy-to-use platform that’s able to go very granular with the data we need to collect. In this series, I will discuss how to configure Google Analytics, how to make sure the data you receive is actionable, and some common misconceptions about the platform.
Are you a marketing or IT manager who’s confused when navigating Google Analytics? Wish you could see only key performance indicators in one place? Or, do you want to share only some of your data in an automatically updated report? Kalamuna has created a Google Data Studio (GDS) report template to help our clients better visualize their data, and because part of our mission is to help colleges and universities meet their goals through technology, we’re creating free reports for higher-ed professionals now until April 30.
Every year I try to attend as many industry conferences as possible, but over the years I’ve become more selective about which ones I go to. I find them to be incredibly valuable and insightful, but they also cost money and take time, so I grade them pretty hard. This year I had the pleasure of attending several UX-focused conferences. Each was great in different ways, and I came away leaving inspired each time, and wanting to share some of the lessons I learned, so I wrote this blog post.
This Friday, November 4, I’ll be playing XCOM 2 for 24 hours to raise money for Extra Life, a charity that benefits Hospitals in the Children's Miracle Network. My game of choice also happens to be a very sneaky way to secretly train up project managers, like some kind of modern day The Last Starfighter. So how can fighting aliens make you a better project manager?
A long time ago, in an agency far, far away… Darth Salesman has just handed over a long-winded statement of work to the green project manager and beleaguered discovery team. Confusion and despair ensue. How is the team supposed to know exactly how to proceed? What kind of promises, parameters and expectations were made beforehand? What tone should they take as they work with the client? How can we bridge the gap between the sales process and discovery phase?
My last post focused on the Information Architecture phase and our method for establishing the client goals, website metaphor and site elements through investigation and science(!!!). It is with this information that we will construct the website wireframes for the client's review. If you are unfamiliar with wireframes, they can be generally described as stripped-down "sketches" of what the site will look like before beginning the more formal design and development phases.
Creating a website can be likened to making a custom car or house, but with a few quirks. A website is not only supposed to be an efficiency-enhancing tool for the person or organization that paid for it, but also a reflection of the organization's persona and agenda. Creating a visual and interactable representation of these concepts takes a significant amount of creativity and testing. The job of any web shop should be to work extensively with clients to pull out exactly what the group's goals and needs are for the web and to translate them for the internet.
We here at Kalamuna believe in the power in science, and aren't in the business of making leaps of faith in regards to web development. We try to avoid superficial "let's hope for the best" scenarios with all projects, and aren't interested in putting ourselves or our clients in painful situations.