Skip to main content

How to not kill a good idea

By
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.

Example
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.

Cause
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.

Solution
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.

Conclusion
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.

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Azure Service Bus - How to extend the lock of a message | RenewLock

By
In this post we will discuss about Azure Service Bus Topics and Queues, with a special focus on Peek and Lock feature. Introduction Azure Service Bus is a messaging system that allows us to send messages between different systems in a reliable and easy way. A lot of concepts from ESB are implemented by Service Bus, allowing us to do do magic stuff with messages. There are two ways to consume messages from Service Bus Peek and Lock - locks a message for a specific time internal and notify Service Bus when we want to mark the message as processed (removed from Service Bus) Receive and Delete  - once a message is received from Service Bus, it is also deleted automatically from the messaging system Peek and Lock When using Peek and Lock, by default we lock the message for 60 seconds. This means that in this time interval the message is not available/visible for other consumers. Once we process the message we can mark it as processed. If we don't mark the message as processe...
Post a Comment
Read more