Skip to main content

How to not kill a good idea

When you are starting an initiative don’t expect people to jump into the boat with you. Even the best ideas can fail because of this.

For example if you want to start a learning program you should think twice about how you can convince people to join the program and participate to it. In the first moment everyone will say that it is a great idea, this is something that was missing and it will add extra value to the group. But in the moment when you send a ‘mass’ invitation to people, to see who would like to join the program you will have 0 people that would like to join the program.

In my personal opinion, the way how you recut people to a new program is wrong. Don’t expect people to jump into a new boat, to a PoC. They have a lot of things to do and even if the idea sounds good, you are still in the PoC phase.
You cannot guaranty to them that there is a real value for them. This is why in you ask the ‘mass’ nobody will be interested directly. The way how you try to gather the first group of people is not very good.
You may find some people that has stamina and are open to do different things, but is pretty hard to find this kind of people.

A better approach may be to go directly to a small group of people, which you know that have stamina and would like to join the program. Invite them to a private group. In this way you will be able to ‘spark’ the interest to people and form the first group of people that can be used to run the PILOT.
Once the PILOT was run, it will be more easily for you to attract people. Based on this approach, people from the private group can start to invite other people and so on. You can end up with groups of people that were formed only based on private invitation.

Ideas and initiatives are very good, but a good idea is not everything. We should be very caution at the way how we implement and put in practice an idea. A bad approach can kill even the best ideas before they are born.


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…