Earlier this month, Matt and I attended the CU Water Cooler Symposium. Here are three takeaways.
Join the Filene Research Institute and Trabian for an interactive two-day innovation and prototyping session in Chicago on December 16 and 17.
We paid our waiter, walked across the parking lot, and got into the rental car. It was 9:42 PM in Girdwood, Alaska. I pressed the home button on my iPhone to select a new Spotify playlist for the drive back to the hotel. "51 minutes to E Dimond Blvd. Traffic is normal right now."
I once worked in an organization whose CEO repeated in 90% of meetings he attended, “People don’t want auto loans; they want cars.” He also loved making exceptions at the front-line, lending on character over credit score alone.
When’s the last time you removed a product from your line-up that hadn’t taken off the way you expected? A product whose relevance had passed?
To do “agile” correctly, both sides (development and decision-makers) need to get on the same page on what that means. The original Agile Manifesto remains the right place to start.
I've lost count of the number of economists I've heard during ALM meetings, conferences, and planning sessions say annually for about seven straight years now, "Toward the end of this next year, we'll see rates start to rise." When it *does* happen, though...
In this important stage of product design, when working with your development resources here's what to bring.
$71-billion Bank of the West discusses their approach with American Banker.
We're passionate about our craft and spend significant time and effort exploring the (near) future of web and mobile development. We'd like to share the results of that research in hopes that we can learn together.