Skip to main content

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

Popular posts from this blog

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

Construction issues resolution in Sydney - part 17

It's been a while since  the last post In January 2016 the owner lodged an application to NCAT against owners corporation to fix three major defects: - waterproofing of large windows in the living room and bedroom which led to windows full replacement - bathroom drain fix - planterbox fix The owners corporation didn't come to mediation and tribunal ordered to fix all defects within 2 months (the deadline was 8th July 2016). The owners corporation as usual didn't rush to comply with the order regarding two items: bathroom and planterbox. The windows works started end of April 2016. At the same time owners corporation decided to check whether it's a warranty and original builder should fix the issues. That was also related to the fact that the variation was submitted by the current contractor who started fixing the defect. So the owners corporation stopped all works in the middle and went off for a month to "make decision". The decision was mad

Wine - 2011 Brown Brothers Crouchen Riesling

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