Some wise and seasoned professionals gave me some good advice over the last three years.
- Show me the output.
This is my paraphrase. To others, it might be stated as “a bias for action”. Either way, I try to remind myself that the point of work is to produce. - Have a methodology.
Not only will being methodical help order my work, but also it reduces stress. I’d rather spend time creating solutions instead of winging it without a methodology. - You are entitled.
This one has a wide range of meaning and applicability, from getting what I need to do my job to getting some distance when I need it. - You are not the client.
This work is all about relationships and teamwork, but I am the advisor (and sometimes only the catalyst) – not the client. - Are you hired to do what you’re told, or is it your job to make expert recommendations?
Like the others, this question had a profound effect on me. I see all the ones I look up to following this rule. - Finally, from the great Tom Peters: Fail. Forward. Fast.
This small phrase sums up so much great advice. Basically, it means “make mistakes”. Got an idea? Act on it, fast. Learn from what worked and what didn’t work. Fix it, extend it, start over, rebuild it if necessary. But make progress. See what didn’t work and learn from the experience. Iterate.
2 Comments
I’m going to use some of these in my work — thanks, Paul. Especially like the Tom Peters.
One thing that I was told by an amazingly prolific and respected academician who I did research with all last year — “If you can’t explain what you’re attempting to do as a process then you don’t know what you’re doing.” It’s pretty startling how many times assessing this one issue with my subordinates when they’ve hit a wall uncovers the primary problem: a failure to fundamentally understand what they are doing.
All of that is very good advice. I especially like the idea of “Fail. Forward. Fast.” Its the truth, and its the way that ideas turn into great projects, and great projects turn into failures, and failures turn into ideas, and those ideas become even better projects and then output. Interesting concept.
The question – its true, but I guess its defining what your job is first. At the moment, my role (as we call these things in mouseland) is not well defined, and I am learning far more from that than if I had a specific job title with specific responsibilities. Its more that I’m there as part of a team thats re-imagining the way our business works, and its a fascinating process to be involved with.
Interesting thoughts!