From the maker's perspective...

-
I came across this article via LinkedIn. It reminds me of the Maker Schedule, Manager Schedule discussion except its from a maker perspective. Given that I have been doing a significant amount of development in Ruby on Rails for UrbanBound for the past 3 months, I'm following a maker's schedule again. Being my own boss makes things simpler, however I think its important for makers to understand how to be productive and articulate to their management how they can be best managed.


If this seems a bit counter intuitive to you. I can tell you that good managers do know how to manage. However, given all of the pressures around managing a business, its easy to fall into the trap of thinking about management objectives over the needs of the people who getting the work done.

A healthy reminder:


7 Things Highly Productive People Do

Popular posts from this blog

Applying user centric design to your business plan

-
Image
Image by Lars Plougmann I got asked by an investor recently how we at Digital H2O do design. I liked the conciseness of my response and thought it was a good example of how to tie user centric design into a business plan. Here goes: Our design philosophy is best described as user centric design. Our goal is to only design and build features our current, or potential customers, find valuable and that substantially help our business continue to grow. We spend significant time listening to our customers’ needs throughout the sales process. We then form hypothesis what customers’ needs are and what they can accomplish in the application. While designing features we show mock-ups and prototypes to customers in order to get feedback and incrementally improve the design. After the product is built and released we continue to test our hypotheses about how customers will use features we have built. We utilize automated event tracking in the app to monitor u
Read more

Your Inconsistent Design Makes Me Worry About Your Entire Product

-
Image
This is from a product I use daily. Who wrote this code and thought they were done? Who approved these two button styles next to one another? I have this vision of a developer choosing a library that made their development life easier. I picture this code going straight into production use without review. Next, I picture the designer who works there rolling their eyes, checking out, and heading to LinkedIn to see what other opportunities exist. I'm being unfairly harsh, but it makes me wonder what other sloppiness is happening inside this product.
Read more

How to start a product redesign - a playbook

-
Image
A few months back I was working on a large, ground-up redesign for a product I own. I had a little trouble getting started. I realized I needed a playbook to remind me of the basics. I am sharing my playbook for those who are having trouble and procrastinating getting started. Enjoy. Before you start At the highest level, in one paragraph, what is a representative user's goal and the problem you are solving for them?  If you can't answer this succinctly you have many, many features or you don't know your users well enough to continue.  Slow down, answer #1 for each feature set before you go to #2. What's working for them now? What's not? What you need to design for them Verify you are building all the tools they need. Show the process they will use to reach goal - give them a map or trail to follow. Indication of progress toward the user's goal - "You are here" Make sure you build in escape hatches because they find a better way.
Read more