It happens. You’re humming along doing your work and *ding* a project lands in your inbox that you didn’t see coming. Not an uncommon occurrence, right? It is inherent in our industry that this happens: whether it is a last-minute project due “yesterday” or a project that stretches you waaaaaay
Remember the old but classic awkward first date story about the person who goes on a blind date and hears “Enough about me, what do you think about me?” from their dinner date? While we all want to avoid that situation, having people want to talk about themselves and their
No, I’m not talking about Survivor: Market Research (how fascinating would that be!), I’m talking about ethnography. Mobile ethnography specifically. As you know, ethnography is the practice of spending time with a subject group to better understand behaviors, interactions and overall culture. Researchers have long been facilitating ethnography projects: observing
Python, C#, PHP, C, C++, Java, Perl, D3, R, Ruby, Swift, Go, and more… The list of programming languages reads like alphabet soup, and every year a new language seems to enter the market. There is increasing pressure for workers both seasoned and new to the marketplace to learn programming
Let’s engage in a little “stress test”. When you think of customer satisfaction research, do you: Wonder how your organization will actually use the results when the project is done? Worry that you don’t know enough to anticipate likely roadblocks? Feel a bit stunned by some of the proposed budgets?
Do you have a favorite job interview question? Some like the Google-ish interview questions like: “How many ways can you think of to find a needle in a haystack?” Others like case-based questions that have you problem-solve out loud such as: “”How much time does it take to relocate an