Skip to main content

Tom Peters: 100 Ways to help you succeed

Every now and then, I find Tom Peter's Dispatches from the new World of work a lot of fun, including his earlier posts on bad advertising . His blog page logo states "Lead the customer" which actually links very well into Craig's latest post on "The Customer Is Not Always Right" (great post Craig).

But his 100 ways to help you succeed are quite interesting to read. #44 states :
"Are you ... Hip? If not, what ... EXACTLY ... do you plan to do about it?"

which created a number of comments about how hip wasn't really a good success strategy at all. Here's where I think the readers were wrong (as posted into his comments as well)

Apple is a "hip" company. Why? Because they CONSTANTLY redefine themselves.

You're hip if you are able to change (and change successfully) to the point where people or customers look to you for that fresh state that says 'that's where we want to be'.

Yes, what constitutes "hip" changes regularly - so therefore, as a company, do you embrace change and provide that leadership into what is becoming popular (before it does so) or do you follow the trend?

The "hip" people typically drop a trend once it gets too popular - that is , they go find ANOTHER market to conquer.

That's not to say that you should just drop what you're working on for the sake of being "hip". But you need to be able to turn on a dime if what you're doing doesn't make sense or isn't going to change what you want to do. You need to be able to convince people that you're doing is really going to "Change the world" which is exactly what "hip" people can do - inspire change.

100 Ways to help you succeed

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...