About entrepreneurs

Don't know exactly why, but when someone introduces himself or herself to me as "aspiring social entrepreneur" my first opinion - this person is just useless in terms of doing any real business together.

Of course this perception may not be correct in some cases.

I think that's because of several factors:

1. When someone says "I work in engineering (construction, law, education, government, marketing, IT, farming, manufacturing, dosomethingreal)" you can say that at least you see what skills and subject area knowledge you could leverage as a team to build something or to work on some initiative or project.
It also shows credibility of the person, because it at least gives us an idea of what we could do exactly together as a team. Of course other wonderful skills and capabilities may be uncovered during the collaboration, but if initially there is a team of only people who call themselves "entrepreneurs" - nothing is going to work and we will never get any positive result. That's because of the next factor.

2. In general "entrepreneurs" don't do anything useful themselves, but just talk, produce some notes, spend time in meetings, conversations etc. I agree this may be a good business, but as a resource to build something 95% of those "entrepreneurs" are just useless.

3. Devaluation of the term "entrepreneur". From experience, majority of so-called "entrepreneurs" are just adventurers who pretend to be smart and take advantage of someone else expenses. They roam around searching for people who would like to buy their ideas without producing or delivering any value.

I trust specialists, not entrepreneurs.

Comments

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi

Travels etc.

Search This Blog