So, you have a great company. You’ve worked diligently to create a supportive, energetic, enjoyable work environment. You pay your employees well and reward them generously when the organization does well. So, why do they still leave?
It’s extremely easy for an owner or executive of an organization to be bewildered when employees leave. Especially if the departing employee never hinted at any discontentment. So how can you ever know what’s truly in the minds of your employees? I’ll let you in on a brilliant secret… you can’t ever know for sure.
meltmedia is not a typical interactive marketing agency.
Nearly half the company’s employees are technical and actively develop code. We don’t outsource any of our technology needs because we have plenty of expertise in our Tempe, AZ offices. We don’t call ourselves a “Java shop” or a “.Net shop” because we know how to make use of the best technology for any solution regardless of what language or platform is popular at the time.
We are a company of passionate people. Over the past year, we’ve focused our passion on the practice of automation. The following quote is of great significance and inspiration to us:
Machines need to be productive. People need to be effective. – Jim Benson & Tonianne DeMaria Barry, Personal Kanban
As you read this, Apple has already deployed iBeacons (referred to from here on as, “Beacons”) in its US stores. shopkick is testing its own Beacons in New York and San Francisco. A number of Beacon vendors are shipping their own versions of Beacon hardware to developers (we have several in-hand here at meltmedia). The buzz started when a slide at Apple’s World Wide Developer Conference listed the term, “iBeacons” among a myriad of other technologies being introduced there. Once the industry figured out what the term meant, it went all giddy about Beacons and for good reason.
We met 5 times before the hackathon began to plan our app. When the Node Knockout finally came, we were ready. We broke up the 48 hours into shifts, and after a lot of beer, coffee, and sleepy status updates, we finished our app with an hour to spare.
UPDATE: FLTR is now live at flitter.io!
meltmedia has something cool we’re going to share with marketers and digital professionals. It’s called FLTR: Forward Looking Tech Radar (pronounced: “flitter”).
The digital marketing landscape is populated by an overwhelming glut of buzzwords, technologies and tools. FLTR will provide you with a quick visual indicator of trends in technology that are relevant to you. At a glance, you will see which tech topics are trending toward more or less relevance in the marketplace. With FLTR, you will be able to move backward and forward in time to track the history and predict the future of these “bogeys” on the radar screen.
In July 2010, we had our first beard-growing competition–AKA “beard-off”–and it ended in just 17 weeks.
We started our second competition in November 2012 and it’s. still. growing. Er, going. Only three of the original seventeen competitors remain and we’re forty weeks into it. Yikes.
So really, why?
Earlier this year, friend and former meltmedian, Nick Crohn and I were discussing hiring challenges over lunch. The question of the day was, “How do we attract great talent to come to Phoenix and keep them here once they do?” We easily listed handfuls of reasons we love living here and it dawned on us. We spend a lot of time building up and promoting our brands and projects, but we spend little time talking about Arizona. Our state has a lot to offer and so why.az was born.
We wanted to avoid a sales pitch. Our first goal of WhyAZ was to share honest and real reasons why we love living and working in Arizona. To provide interesting, digestible information that many may be surprised or delighted to learn. Our second goal of WhyAZ was to make the site visually and technically interesting with hopes designers and developers might appreciate the aesthetic and examine how it’s built.
When deciding what approach to take, I thought a lot about what makes web design exciting for me. In May I attended CSSConf in beautiful Amelia Island, Florida. One of the recurring themes was the blurring between design and development and utilizing CSS3, Sass, and browser tools to enhance our designs. With only a few lines of CSS, we can easily duplicate the intricate design work we’ve previously reserved for Creative Suite. As a designer who prefers to work in a text editor, it really is exhilarating to type words and numbers and see pictures come out the other side.
Ten years ago, Dave Shea announced the CSS Zen Garden. His original goal was “[…]to create a page that allows for some wildly different CSS designs, while coding valid XHTML 1.1, valid CSS, and conforming to Section 508 and AAA accessibility guidelines.” It is a single page of HTML that you can apply any of 213 CSS stylesheets to.
Back in 2003 seeing the power of using CSS like this with valid markup wasn’t revolutionary, but the idea of separating content and style was. The Zen Garden made people re-think how they made web sites. The internet was filled with nested tables and inline styles at the time. And just two-and-a-half weeks after Dave Shea announced the CSS Zen Garden, Jeffrey Zeldman published the first edition of Designing with Web Standards. It was the beginning of the Web Standards Movement.
Since then it has become the industry standard to keep content and design separate, and to write HTML and CSS that is valid according to the standard set by the W3C.
AF: The other day you and I were chatting and you asked me, “How would you define a company’s culture?” I had to think about it. Generally when you ask me questions, they’re loaded or you’re expecting me to crack a joke. Seriously, I had to think about it.
Then I had to think about it more. I thought a little more than that. Then I thought for another 2 seconds or so. The on-the-fly answer I gave was a little like this: “I guess I’d always considered culture as the combination of the environment of an organization and the sum of the personalities in that organization. It’s the way people work and the way they interact. Maybe a little of the space in which they work is mixed in there for good measure.”
AG: Well, the reason I asked is because I’ve been reading a lot about company culture lately. I liked what I was reading, but I wasn’t really sure all the different authors were defining “culture” in the same way. And then I realized that I didn’t really know how to define it myself. And then I realized I should probably put some pants on and leave the office.
So, I started looking for more formal definitions of company culture. There are a lot of great articles about culture, but very few articles actually defined how they were using the term. The Harvard Business Review even went so far as to ask, “What the hell is culture anyway?”
Part 2: The “Why” and the “Why Not”
If I counted correctly (I can count to 2, for sure), this is the second and last article of a two-part series. In this article, I write about the pros and the cons of each of the three methods for building a mobile app.
Typical Timelines for Mobile App Development Methods
The three major stages to most software development processes involve design, development (coding) and quality assurance (QA). The chart below attempts to show a rough comparison of those project timelines for an imaginary mobile app project that involves three platforms (iOS, Android and Windows) and the web. Based on past experiences here at meltmedia, the impact on time is shown by the length of the bar, as a percentage and in actual (imaginary) hours. Actual miles may vary, of course.
We’ll refer to this chart in each of the three sections below. For the sake of having numbers that we can wrap our brains around, our project chart up there shows (vertically and by color) the three main segments of a typical application development timeline: Design (orange), Development (green) and QA (blue). The imaginary “Native App” project has three tracks (iOS, Android and Windows) of 250 hours each (62.5 hours for design, 112.5 hours for development and 75 hours for QA), totaling 750 hours for all three platforms. The “Hybrid App” project will total 550 hours. The imaginary “Mobile Web App” project (the bottom track) will take 250 hours total for design, development and QA.
Over a year ago we released a small collection of free icons on our blog. As it turns out people liked them, and not just because they’re free. So in keeping with the spirit of being Interactive Superheroes we’ve made a new and improved set, and we’re calling them melticons Mk 2!