Blog.

gb

56 posts tagged working well

An Excerpt from The Book I’m Writing

Although I remember a time or two that Blankenship has hinted either on Twitter or his blog that he’d like to write a book, this is the first confirmation I’ve seen that he’s actually writing one.

I have no idea what it’s about—though I have some guesses—but I’ve been following his blog for years and he’s certainly on my short-list of folks that I’d like to see some longer-form thinking from. Good stuff.

Bring me stuff that’s dead, please

Interesting perspective. I like it. Sometimes staying relevant—in the pop-culture sense—is really just a popularity game, while the real work that makes real breakthroughs and real money is quietly being done out of the spotlight.

Why work doesn’t happen at work—part 2

Or: On Where I Work

“Where do you go when you really need to get something done?”

This post is related to Jason Fried’s short TEDx talk on Why work doesn’t happen at work, so start there.

Jason asks an important question: Where do you go when you really need to get something done?

This is a topic that has fascinated me for a long time. I’ve thankfully—and I’m very grateful for it—had the freedom to work how I please, for the most part, over the last few years, since I work for myself and I’ve learned some things. That said, the patterns that I’ve fallen into aren’t necessarily working for me just because I’m not an employee. Depending on your personality type and the work you do, I think some of these things might work for you too:

Why work doesn’t happen at work

Jason Fried at TEDxMidwest

This is a great TEDx presentation by Jason Fried of 37signals on the office and why people don’t get much actual work done there in a traditional setting.

He asks an important question: Where do you go when you really need to get something done?

I started writing some of my own related thoughts on how I work and it turned into its own post.

Giving Better Design Feedback

A great article. I’ve seen it linked to from several places so I wanted to pick a quote that hadn’t spread as widely.

The main point: hire a designer because you trust them to use design to help solve your business problems. Remember that that’s the framework for your interaction with your designer and move from there. Losing this perspective is what usually makes a project go badly.

The Industrial Age is Dead - Time is the New Money

I agree with my dad on this one. When we can make our world both smaller in connection (through place, use of technology, etc.), but more diverse, the potential for community growth is amazing.

Starting is easier than sustaining.

The more I work on my own web services and the ones I’ve built for my clients, the more this idea resonates: starting and building the project is the fun part. Maintaining it is the real work. That’s not to say that running a successful application isn’t fun at times, but it’s very different from the blank slate with endless possibilities that you started with.

John Sculley On Steve Jobs, The Full Interview Transcript

And, following on the heels of the last post… The differences between Apple and Microsoft have been studied to death, but only because they’re so damn applicable to any organization we come into contact with. I’m a designer, I know I’m biased. But I’m also a developer, and a business person. Design thinking should lead in an organization. And, you don’t even need someone with the title of ‘designer’ to have a company culture that values design thinking. 

Laziness

So true, and I’m so guilty of succumbing to it.

Presenting Design Like You Get Paid For It

I’ve done both in my career. I’ve shown design options and let the client create a Frankenstein. And, I’ve shown the client what they need and helped them understand why they need it. Option #2 is always more successful for everyone involved.

More-so: I never design something based on presentation option #1, so why would I ever present that way? Showing clients that I understand their problems and helping them understand the solutions I’ve come up with leads to a more successful project, and makes me more valuable as a problem solver. Ultimately, I’m not a designer. I’m a problem solver.