Browsing Category

Practical examples

Avoiding problems, Practical examples

Software architecture to scale business

August 25, 2019

Software is present in every organization that wants to grow at some scale. The software helps the company’s employees to be more productive and to reduce manual and repetitive works. The software can have the best possible interface, turned 100% to people productiveness, but as a basic item, it must work when it must work. When vital software to an organization fails, the difference between regular software and good software is discovered. And here I talk about its architecture.

When the architecture makes the difference

To talk about this subject, I’ll cite two real cases of two clients in the media area. They are close to me and had their business growth held for some while due to bad quality software.

Please, no more load

The mentioned software was a portal to Brazillian population access to a known TV show. With that portal, people used to register themselves to be part of the TV shows, donate money for good causes, interact with their favorite characters, and some other activities. Under normal circumstances, the portal used to handle everything. But when one of its TV presenters mentioned something about the portal when they were live in national network, it was deadly. We just had to count time and few minutes after, the portal was down. It could be simple stuff like saying live “access our website for a chance of winning a prize”. Or “access our website to talk to the actress X”. And the problem that repeatedly happened, taking the portal down, was a technical problem related to its architecture. It was not prepared to receive so many access like it did in fact. In this example, we see a powerful trigger to an entire population being wasted because of a software malfunction. The population (customers) already convinced to look for something, was frustrated with the malfunction and lost interest automatically. The TV show image was affected negatively, and he failed at enhancing its brand, increasing its overall engaged public and eventually losing some revenue.

Let’s integrate!

The second example is about a scenario when the software was a big aggregator of information coming from many different sources. It was responsible for some important transactions related to the company invoices. It operated fine for many months after its first release. But when the database went over some load, it started to behave slower than it used to. Also, a big project or renewing the entire UI was undergoing. But it would be a big failure if something beautiful was released without actually working. The loading screens were too slow and were forcing the user to wait for many seconds for some feedback. The impact on business was quite relevant because the selling process for a few of their products was also affected.

Solutions and business relief

For both of the scenarios, a new architecture was implemented. The first one focused heavily on caching. The second focused on shortening the times to get information. But both passed by a deep architecture remodeling.

Nowadays the first one counts with millions of users reaching their portal to interact with the brand. They also count with a stable portal, which allows the decision-makers to make wiser decisions than when they were under pressure. The second was able to release the new UI, which enhanced the relationship with B2B demanding customers, and no more transactions are lost. Now the roadmap is welcome again.

Avoiding problems, Practical examples

4 Minimum artifacts for an IT cascade-agile project conduction

June 2, 2019

Whenever we are running an IT project, if we already have a deadline set before the start, no matter what, this project will turn into more a cascade than an agile conduction. Besides this status report, I’m listing the minimum artifacts to have a successful project being delivered.

The scope

The scope is basic. It is the base for everything to come. You will extract everything from the scope: the schedule itself, the pace you have to go to keep the schedule, and the team to reach everything. The key information that must be in scope are:

  • The requirement list;
  • The details of each requirement;
  • For who is that requirement applicable?
  • Who has validated the details?

Optional:

  • The time estimates to reach that deliverable;
  • Who is needed to perform the technical part (strong dependencies only);

You don’t have to hold the fanciest document. You just have to hold a document that everybody involved can understand. I’m suggesting this document model.

The schedule

As soon as you have the scope, you will be able to start taking operational decisions. What are the restrictions you have for your schedule? What team is enough for you to reach the given deadline? Can you beat it earlier than planned? Always plan to finish the project before your schedule says, and keep some margin for the problems to come.

The key information that must be in your schedule is:

  • When will you deliver each requirement;

That’s enough. I strongly disagree with going anywhere beyond this point. Otherwise, the project manager will dive to an endless cycle of micro controlling everything. Issues will come with simple or complex documents. Go ahead and create your own model. List the requirement and the date to be delivered;

The status reports

The status report is a weapon and should be used wisely. It can be used to mark milestones for the project and also to create a sense of urgency for some scenarios. It is a powerful weapon. Do not avoid using it. Here you can find the model I’ve been evolving for years. Some of the key inputs:

  • What changed from last status report to this new one?
  • Who are the responsible people for taking decisions on this project? At least one on the delivery team and other on the client (internal or external) team;
  • Where are we in the schedule? Do use percentage here.
  • Major executive items (green/yellow/red) like scope, people and schedule;

Still in the status report. Always remember: if people are asking you for a status report, it means a huge problem. Not sending or wanting it, but the act of asking for it. If they ask for an email to get to know how the project is going on, it automatically means they are not involved as should be on the project. If the status report is green, everybody knows it. Or if the status report will have bad news, everybody must already be feeling the bad news.

The scope changes

Since you are running a cascade project, be prepared for scope changes. I haven’t seen a single project where they didn’t happen. When I hear a scope change, I know I’m walking the wrong way. But it makes me happy because I’ll have the opportunity to put things back on track before the end of the project. Keep track of all scope change requests coming from all the team involved. Make it very clear those already approved and those which won’t be pursued for any given reason. A scope change track document will have the following information:

  • The new requirement OR requirement changed;
  • The description of what’s changed;
  • What’s its impact over the schedule;
  • Is it included in the project or not?

You can use this model to track the changes. Once they are approved, they must be listed as a new requirement in your original scope document.

Others

Few other activities will require you to have a kind of formalization. Using email for that is enough. Some of them will be:

  • Deliveries approval;
  • Changes approval on scope and schedule;
Entrepeneurship, Practical examples

Successful negotiations

February 20, 2019

When we talk about services industry, unless you are in a niche not explored or own an entire market, it’s hard to show trustworthy credentials and proofs that you should be the one chosen (showing you are better, you deliver in time, your quality is world class, etc). Almost everybody can say they are good at doing what you do, even if they have never done anything like that before. This affects sales directly in a market where the competition is huge like the US. Getting into scenarios where we have at least 3 competitors, and some times more than 10, is pretty common.

In 2018/2019 I’ve been successful in the biggest part of sales negotiations I got in. For those which we didn’t win, at least we figured in the final shortlist. They all have different stories like where we met people involved, the percentage of how much the negotiation was done physically or not, how many steps each one of them had, the client’s size, and many other things that influenced on the results.

The common thing for winning all of them, from what I’ve seen this far, for sure passes by how much you can show of your technical quality not using technical stuff. The one who signs the check usually is not someone technical, but wants to feel comfortable on choosing us. Making them comfortable someone appropriated is going to handle the situation is the key.

But after winning, a feeling, or even a testimonial, comes about why did we win each one of them in specific, I mean the strongest reason in particular for each of them. Below I listed some of those main reasons for some companies, described a bit the scenario involved and shown how we prepared for some of them.

Speed and coherency in communications

Being fast and coherent on your communications is something decisive. If you go too slow, your client will end up thinking they are just one more in your list. Some studies say that your first answer must be within the first hour the client contacted you. For the next steps it may vary a lot. Being fast brings the feeling that you are dedicating energy to them. Beyond that, the speed with coherency creates trust between the parties. By coherency here I mean saying NO when you have to do. When you say no for something requested you are creating anchors of truth (that you will have to proof they are true in the future), and also is decreasing the strength of vendor-client aggressive relationship that some partners try to proceed.

Dedication on understanding the scenario

Do dedicate yourself on understanding the scenario. For sure this is the step that will give you inputs for everything mentioned here. If you don’t know the partner’s scenario, you simply are not up to help them. Dedicate on understand what is the business scenario, what you really have to deliver, but also spend at least 30% of your time understanding the consequences of each scenario. Why is that company buying from you? Do they have a strategic move related? You will know that and get more information to look even more trustworthy just knowing your client’ situation.

Be flexible. Give alternatives

For many of the negotiations I got involved in, there was a mental clock running out of time for something to be solved on the partner’s organization. If your client is under pressure, he needs alternatives. Period. He needs something he can realize is better for him so he will sleep comfortably at night. If you go for a negotiation with one scenario of purchase, you are losing the opportunity of being 2, 3 or even more alternatives inside one partner at a time. If you go for the scenario with more than one alternative, you will show empathy with the situation and also will show flexibility. You solution and your knowledge may always be the best in world, but sometimes it’s more than what the partner needs. He just needs to solve a problem, not a rocket.

The setup for the moment

Unquestionably, my favorite part for every single negotiation. The moment at the round table. The table must be round. For all of those I got involved and I remember while writing this article, we wanted the long term approach. We didn’t want just to have a deal and never show ourselves again. We want that deal to be successful, because we want more deals and also referrals for more deals. A lot of techniques can be applied for this moment, but it is a matter for a single article and I will resume here in three steps:

  • Preparation – know everything. The scenario, the people involved, the implications involved, etc;
  • At the table – prepare for that. Plan ahead each move and each question that might arise at the table. Be prepared for a money negotiation;
  • After the table – you went so far, let’s now miss the deal with small mistakes;

Use credentials

For every moment of contact you are allowed to use credentials. Credentials can be a lot of things like telling a story about a project your company delivered, for how long the company exists and handle challenging projects like the one you want to talk, even cheap chat can show credentials for some unformal scenario. The goal for a credential is to increase trust in something that will help the negotiation move ahead. But the one who got my attention and was not in my speech at the beginning of my journey was telling how many years I’ve been working in my company. The perfect scenario happens if the customer ask you that, because will show he’s interested. But you always can mention that to leave one more strong anchor.

Decisive factors exposition

In long-cycle sales like my reality (having more than 6 months between knowing a company and signing a contract), it’s close to arrogance to think that what you heard for the first time when you met your client as his business goals will remain exactly the same 6 months later, when you are at the round table negotiating. Whenever you have a chance, ask key questions to check if you are delivering what the customer expects. Be straight on that. That’s simply the reason you are being hired. Ask that and double check whenever you can to check if nothing has changed. At the right time make it visual to create a mind-contract between you and who are signing for your services. This is the only way for you and the partner have the same feeling that you are going to deliver what they need and want.

I hope these thoughts I gathered during 2018 and 2019 (this far) help you to be successful in your upcoming negotiations. Use the space in comments to ask questions if you want. Let’s talk!

Digital transformation, Innovation, IT is business, Practical examples

5 reasons to start and speed up digital product management

November 4, 2018
Digital Products

One of the main objectives of a well-planned Digital Transformation journey is the creation of Digital Products. Having Digital Products means that some of the core systems of the company can be turned into a product or service. Other partners can benefit from! Or even your data will allow you to create new products that didn’t exist yet. That means new revenue streams, not necessarily aligned with the current business.

Some examples are famous and some of them are pretty new, showing that to create useful Digital Products all you have to have is the will to make a difference:

  • Retail started what we can see now. Then banks came with their apps, home banking, credit cards, insurance simulators and etc. All this Digital Transformation reality got strengthen with them;
  • BTG started in 2014 what nowadays is the SnakeBite911 app. With that people can collaborate and mark where they’ve been attacked the most by snakes. For BTG, they are offering clinical trials and have many other offers to come.
  • Vivino is a social network for wine lovers. A score for each wine and many other details can be added by the user. Vivino has been using the app to offer wine to the huge number of users they got.
  • Companies that sell farming fertilizers are mapping region’s soil, the weather forecast for the year and the next, and many other data. This way they can suggest their clients which fertilizers they should buy and when to buy it;
  • Health: apps who help runners to monitor their evolution, tracking how people feel while they train and suggest shoes, nutrition hints (and products), next events, etc. Also, smart things (like shoes and swimsuits) are already available, tracking a lot of data, and suggesting a lot of products and services to be acquired.
Be the one pushing the change

Some changes happen on how you and your team behave when you change from project to product-centric approach:

Project-centric Product-centric
Delivery – that’s the mission! Owning – change everything. The culture will change, the will to be part, motivation, etc etc etc
Stay on backstage – yeah, IT usually is just the way to reach something, not the something that must be reached Stay in the front stage – IT leaders start being at the front stage alongside with business leaders
Sensation of completion – leading to… nothing. Just more tasks; Continuous – apply the mindset of improvement, avoiding the team’s sensation that a project who completely satisfies the final client is never delivered

The 5 reasons

1st – “By 2020, 75% of digital business leaders will have abandoned Project model and adopted product management model”opening keynote from worldwide flagship IT event in Orlando 2018. Project model is not fast enough. Every time a project ends, the team is disbanded. Then new negotiations for the new cycle of improvements start. But until its end and the new team come, is waste of time and waste of the team’s knowledge.

2nd – “By 2020, organizations that have embraced the product model will outperform the competition that has not, in both customer satisfaction and business results (Gartner)”. Since product-centric is faster, we must adopt it in order to stay ahead of the competition.

3rd – “78% of companies growing the most on American market are using a product-centric delivery (Gartner)”. Nothing to add here.

4th – “A product-oriented company’s IT department depends less on HR interventions, and takes by itself the leadership of culture and self-development initiatives with internal teams (Gartner)”. The first change is more power and influence to IT. But that doesn’t mean the other areas will be weak. It means they will put strength together to make things happen to have both visions: business-led and IT-led. None of them can exist without each other.

5thEvolve the IT to turn into a hub to attract internal and external ideas, business partners and talent attraction (Gartner).

Having Digital Products in mind, the benefits above are natural, and the reasons to do it are compelling. It’s the fastest way to approach traditional companies to how the unicorns that are changing our economy are.

 

Recently I attended the Gartner Symposium ITxpo in Orlando. Gartner shared some of the insights here (properly mentioned on the links). The rest of them I had while listening to the keynotes.

Digital transformation, IT is business, Practical examples

Why do digital transformation initiatives fail?

September 21, 2018

I’ve been looking more and more for reasons why Digital Transformations fail. Here I’m talking specifically about the steps regarding launching products straight related to experience. Many of the articles are too abstract saying that it’s lack of culture. The culture is hard to change, etc. Some of them are about lack of empowerment, but again it turns to culture.

After reading many of them (some of the most important listed below), I came to this conclusion: it’s lack of will. I’ll explain. Before everything, the articles:

 

They say it’s culture

The most present thing is always related to people. Culture, engagement, communication, expectations clarity, etc. I couldn’t find a single mention saying that the project wouldn’t reach the expected ROI.

Beyond the results that consumers can see, some of big companies’ moves went through internal automation and changes. The great challenge in these scenarios have been to IT and business areas capacities together. If one of the areas had the knowledge of both, they would be only one. This is Digital Transformation.

Clearly the suggestion here is to put them to work together. One cannot live without the other. But the main thing is to remove the competition between them. Now that IT saw that it can add value to business just like the product areas, a competition started. The shortest way to put an end to that: have a single manager. A CPO and a CTO working together, with different responsibilities but with the same results expectations, is a good match.

It’s an internal change

Ford is having issues to real engage with Digital platforms. Tesla is not. What’s the difference?

The will is one step before putting hands to work. When we are talking about the involved teams, the will is the output of contextualization and engagement processes. Leaders that didn’t buy the sponsors idea, won’t be able to pass it on. They won’t engage their teams properly.

Then many things may come to leaders and employees minds when acting in a new initiative. It’s all new for them. They don’t know what will come. Maybe nobody is sure about that yet:

  • Leaders and employees: afraid of what’s new. I know some companies that chill when they hear about agile development. They are afraid of that since the 90’s. Even after watching more and more successful benchmarks, it’s never enough for a real change;
  • Product areas: and that goes all around the company. The product areas don’t know the IT and fear their guys;
  • Operational areas: the operational areas, if aren’t properly engaged, will sabotage everything they see. Sometimes it isn’t even rational;
  • The board: the directors are afraid of doing a new investment that won’t bring the expected ROI, and for many times will decide to keep the organic growth instead of doing something that can be exponential;
So why it is lack of will and not lack of culture?

The will is base for culture. If the leaders are not convinced of going Digital, they won’t do anything. But I’ve already seen some people well convinced that this is the future, and even after that, they won’t make a thing. But if the needed leaders are well convinced, and willing to change, they will be able to change their own culture and their team’s culture to achieve what they are looking for.

Digital transformation, Innovation, IT is business, Practical examples

Health awakes for DT

September 21, 2018

During the past week I had the opportunity to attend to an important trade fair in USA for IT decision makers in midmarket companies. It was an incredible experience to talk to many people who are in charge of the future of their companies.  I got really impressed to know what they are looking for and what are their real concerns by the end of 2018.

Special mention:

Before getting to the real point of this article, I have to mention that I got to know many important and intelligent people. They were looking for the same old solutions to solve problems that were already solved a million times. I saw people looking for solutions that were created in 2007. That’s impressive but that’s also a sign that we all are inside a cycle. And we all are evolving. That’s the coolest thing about the event.

 

To the point: Digital Transformation one more time

It’s not new for everybody that financial industry is heavily affected by Digital Transformation. I can’t find a single bank that isn’t looking for that. Some of them are looking for experience enhancements; others are all about regarding automation. And the majority of big companies already past this phase and are already looking for omnichannel. It’s not that strong when we look for insurance, mortgages and some other industries. They have a different pattern. But they are all in similar situation: evolving.

Beside financial, we’ve heard some real cool moves from Amazon (a benchmark of course) in retail, and many others. But after financial and these moves in retail, it’s being kind of difficult to find the next industry witness for DT.

The health woke up

I had an incredible opportunity to talk to three chairmen for health. They are concerned about some things but they all mean the same thing. Their concerns were:

  •         Stop developing apps without previously validating if that is the real thing their end-user is in need;
  •         Generate business value from IT because of competitor’s moves;
  •         Take care of the little monsters that shadow-IT created and now they have to support;

If we look outside the box, those gentlemen were concerned about the same thing, as their next step for Digital Transformation: engage business areas;

Their initiative is great. But it’s also late. I’ve been discussing the third symptom with financial companies for the last 6 years. That’s always the same: an isolated initiative from a business area innovating creates something new that gets strength in the organization. But they are not IT. They don’t have the needed experience to support this new product/whatever else. Then the IT is called and they say: “hey, now you have to support this”. The nightmare starts. For the first two points, it looks like the company already got some good insights and is trying to actually act seriously towards DT.

What’s their scenario

Since they are looking for generating more value from their business areas, I thought quickly about some issues when I have to do something related to health, also did a very quick research (not more than 15 minutes – Forbes source) for the most common issues on health that now can be solved with IT and will to do:

  •         Disabled assistance: If there’s a disabled patient, let’s automatically call an Uber at the end of his appointment to take him home;
  •         Market knowledge: get to know what the clients are thinking. Let’s monitore social networks with AI and check if they are complaining after an appointment;
  •         Accessibility: a lot of paper is sent to people when they have to pay for health services or when they just use it. Let’s group all of that digitally;
  •         Accessibility: there isn’t a single repository that a doctor can access all of their patient’s history in diseases, symptoms and treatments. It forces people to carry a lot of paper whenever they are going to a doctor to talk about something recurring;
  •         Omni-experience (Forbes): I guess I’ve already heard that in financial and somewhere else. There it’s called omni-channel. And it’s coming to health. Here’s what it is: everytime your customer gets in touch with our brand, either online or offline, we must assure that he’ll have the best possible experience. Every point of contact matters;
  •         Health-techs: let’s connect to them. There are many coming and many more to come. Let’s send our doctor the information of our home-based check-up system. Blood pressure, weight and some other stuff can be checked remotely. And will mean a huge difference for some patients.

The same things that are very clear in financial are starting to happen in financial. The main thing is the mindset: having the will to solve the same old problems, digitally. Forbes says: it must come from above. If the health company’s sponsors don’t buy it, nobody will.

Digital transformation, Entrepeneurship, IT is business, Office, Practical examples

How did Netflix reach the nirvana of ownership?

May 15, 2018

Netflix doesn’t have a CTO (Chief Technical Officer). Having a CTO would be a symptom of centralization of technical decisions. On Netflix they have just a CPO (Chief Product Officer), which is the chief for their products. Products and IT are the same. Netflix also is one of the most innovative teams on technology and value purpose on world. But how did they reach this point? What took them there?

 

Profiles and responsibilities

They were born this way. It was a mindset simple to keep while they were a startup in 1997. But this thought have been kept during the years even with company’s growth.

With a set of benefits to their employees, which can be translated simply on freedom for them to take the actions they think are needed, Netflix shares their actions on management and responsibility in their speeches. The main concern of a manager is to hire the best people on world. The main concern of all the employees is to take the best possible decisions, having all the company’s context available to rely on. Subscribers numbers, revenues, all the areas budgets are part of the routine information that the managers share with their teams. Managers require their team members to enroll to competitor’s hiring process at least once a year to ensure they are getting the money they deserve. There is no knowledge management also. When an employee leaves the company, their projects die with him. There are no junior, plenum or senior levels.

 

No rules

Netflix avoids rules and processes because they believe that when you tell people how to act, their creativity is restricted and it makes them to stop thinking on how to add more value to the company. It has a cost. It is common for hiring positions to take more than 6 months to be filled, because they require complex hiring process and high levels of subjectivity.

Having some benefits examples like:

  • Vacation time undefined;
  • Maternity leave time undefined;
  • Technical subjects budget unlimited;
  • Hardware and software budget unlimited;
  • No work plan definition: once you get hired nobody will tell what you have to do. You create your own project, work, finishes, tests, and goes to the next. At this point your manager can help you taking the decision if you want.

This freedom goes through only one restriction: act like Netflix interests.

This way the company, which is proud of saying that hires only the best possible people for their positions, and that has more than 4000 employees, reached a level of ownership hard to compare. Each one is responsible for their projects and has autonomy to define if it is useful to the company or not.

 

What does it generates?

It generates an incredible freedom environment for people to produce what they consider important. Once all the employees are the best in their areas, it is understood that they will have enough knowledge to take the best decisions. It generates more than 100 projects going on simultaneously from all company’s areas and being tested at every moment. IT projects can’t take more than 2 months to be finished. Each 2h one publication to production environment is made, and nothing is activated before going through A/B testing.

The great objective of ownership also is achieved because all of these conditions also have the intention to delegate power. Every Netflix employee must be capable of taking decisions without depending on endless validation processes or unnecessary opinions. Mixing freedom, responsibility and power is how Netflix reached and keeps his very high level of ownership among their employees and keeps being one of the most innovative companies since the moment it was created.

 

The model and how to learn with it

Compared to other companies on different acting areas, among the most traditional ones like industries and the most recent startups, Netflix reached his ownership through the joint of some things: almost unrestricted power, almost unrestricted freedom and seniority/maturity as a premisse.

This is a unique model that should not be pursued blindly, but used as inspiration to watch the disruptive way they found to manage their company

Customers, Practical examples

A good customer experience performance for sales at financial area

May 7, 2018

This article was written by me, Eduardo Diederichsen and Felipe Lindenmeyer. Me and Eduardo are managers of ilegra’s Software Development area, and Felipe is a senior account manager. We all are connected daily to clients demands.

 

Daily we do negotiate with a lot of clients. The hardest part is not giving them a price or conducting a good presentation with beautiful slides speaking buzz words. The hardest part is to identify if the potencial clients have a challenge for real and how its challenge can be approached by our company’s potential, language, market vision, and etc. When we find that out, that client will deserve our deep focus to make a good understanding and offer something that fits perfectly to its needs, even if he doesn’t understands it, but then try helping him understand it.

 

The experience

But what makes a experience as perfect as it must be so a client with sign the new contract? Impossible to tell because who buy from anyone is people. People lay on different things to evaluate their experiences everywhere, giving more weight to different points based on their personality and the influences they had during their whole life.

 

The scenario

This recent new client had a complete journey from the very beginning contact to signing a contract held by themselves in many companies. At the end he decided to buy from us.

The client scenario

It is a client from financial area, so he knows the financial area customers in Brazil are very demanding regarding the whole UX and the products flexibility. Brazil is the country with most developed User eXperience demand in entire world, so the competition and investments here are huge.

First contacts

What happened: the first contact happened in a casual party, not related to work. The subject on the crowd turned to work. We explored very briefly few examples of how we are helping some important companies in Brazil to be in front of their competitors. What really happened: The attention was caught and visit cards were given. Few days later they asked a meeting to talk about our portfolio and get to know their requirements and concerns.

The meeting

What happened: it happened at customer’s facilities. The goal was, as they asked, to talk about few scenarios we’ve been working and the opportunities we identify and foresee as experts at the market. What really happened: they understood we had the knowledge to be their partners and if they count on us they would have oppinions of a specialist in their market. So the next step will be send a proposal and everybody celebrates? Yes, but not so fast.

The challenges
  • FIRST! What happened: they are a very conservative Brazilian firm which still isn’t enrolled to digital transformation practices and doesn’t even want to get to. We are very used to work based on agile methodologies, Lean approaches, testing and discarding losses very quickly. They wanted everything predictable with very clear goals and steps. What really happened: they understood that their competitors don’t work in that way anymore and that working that way they would still be left behind in the competition scenario. Then we reached a mix of practices that would give them part of the control they were asking but giving the project part of the freedom that kind of work needs.
  • SECOND! What happened: they told us they wanted to be in front of their competitors knowing how much it would cost and how many time would take. Well, if I knew that, I would be one of the competitors. And that’s where the Lean and experimenting mindset gets the attention. The startsups bothering giant industries don’t have this kind of answers. They won’t have it too. What really happened: we decided to go for a first deliverable (We can call it an MVP) and a further evaluation after that to redesign the plans.
  • When things got warm: What happened: we had the steps above but it was taking too long for a decision and things got warm (bad news). Our decision was to invite them to come to our company’s headquarters to see with their own eyes everything we were discussing. They really got impressed with our office because it’s designed to give freedom to people think and innovate. This was a key step because they spoke to people who would actually work with their project. What really happened: the deal got hot again.

 

What is faced differently by everyone

There are a lot of subjective things in the explanation of the sentences above. I’m not exploring their body language, neither ours. I’m not exploring the sentences we told each other and how did we look during the meetings. So, I’m not telling how we created empathy here. Let’s get to things close to that.

The client scenario

Some companies can be afraid of innovate. It’s a whole new scenario. People fear the unknown. They don’t know what is coming and then they get afraid and just stop. For other companies, the unknown is exciting and they know from there the innovation will come. They will seek for it as a routine.

First contacts

Since it happened in a social event, the thing was easier. The focus was not evaluation. The empathy came easily because we spoke about our cases in a brief (not moving the whole night focus to work only) and humble way. If we were too thirsty about their needs it could turn into something boring and we could lose that guy’s attention.

The meeting

The meeting was all about showing our capabilities. With that being flexible to understand their concerns about models and what we were proposing. At that time we invested some time explaining and desmistifiyng software development practices like Dojos, Meetups, team management models, our concerns about quality (A/B Testing, Chaos testing, etc). And at that time a big thing happened: the empathy with one of the guys was so huge, he found so many value, that he started defending some of the approaches to the sponsors in a very enthusiastic way.

The problems

We had to use a lot of knowledge to tell them the differences between the way they were approaching the problem and where we see the market moving to. It was hard work to understand how they treat projects and mix it to a reality we could work being sure we would reach the results both of us were hoping regarding the new partnership. But the biggest step taken was the use of the experimentation mindset to go for the first phase. They wanted to give a shot at our suggested model. That’s the chance we had to keep things going well so we would build more trust.

When things got warm

It was the dangerous part. Calling and bothering client’s patience wouldn’t have been the efficient approach. Bringing them to a controlled environment was a good move. Sometimes people don’t get everything you say when you are presenting something. You will have to repeat it in order to get the perfect moment where your explanation will make sense to them and then their attention and interest will be caught.

 

Being more generalist here with a few more examples

One customer may like to hear to most recent buzz words all pronounced in english. Another client, coming from countryside may not like it because he thinks it’s something for bigger companies. The proposal: one customer may prefer a document with a set of beautiful images in a more abstract way. Another customer may prefer to receive a one page document getting straight to the point using just text. It’s unpredictable.

 

Good! How can I learn with this scenario?

The CX (Customer eXperience) gets more challenging to achieve when we are talking about B2B or B2B2C offers. When you have a B2C scenario you probably will have one person at the edge who you have to please with your offer and your advantages. It’s easier to ask him: “hey, did you like this new feature?”. Getting back to B2B or B2B2C the variables are countless, since you will have to deal with many people from the very beginning of the negotiation until reaching the final contract signed.

 

How to attack that efficiently?

Short answer: be interested. Long answer: keep the knowledge with people involved, get experience, and be interested about evolving in the process and the learned lessons. Try to understand things about body language and psychology, do know the one who is buying from you. Does that guy writes publicly? Does he give speeches? What is he speaking/writing/reading/hearing/studying that you can take in count to set up a moment for a fast approach?

Digital transformation, IT is business, Practical examples

Using Machine Learning in real life part 2/2

April 5, 2018

Now that we understood the difference about the three approaches we can have over AI with the last article, let’s dive in into the mid-term approach, always keeping in mind the borders. Given the explanation of the differences between Machine Learning approaches: a) ready-to-use APIs, b) training a model, and c) creating a model, let’s talk about training (using) a model.

Training a model

This is the mid-term approach to AI (Machine Learning) problems. Once you found out your problem can’t be solved by any ready-to-use API, try this approach. Just because there is no ready-to-use API, it doesn’t mean nobody ever tried to solve your problem generically and widely speaking. There is a high probability that your problem already can be solved by an existing model. Using this approach you will have to look for three things. It’s not a dependency, since the third step can be left away in some cases (example below), but they are a sequence.

Finding the best model

This is the part where you will have to have someone with good experience in this subject. There are different models to solve the same problem, as an instance. And there are also many problems without models covering it. You will have to find the best model that fits best to your needs. You will have to check the trust percentage that model gives, if it checks all the information you have, if you will have to adapt any information you already have to use that model, and many other things;

We can split the models into three different groups:

  • Models for supervised training

    It happens when you have the information that the algorithm must reach conclusion X (objective) after evaluating A (info 1), B (info 2) and C (info 3) information; Example: you know that sneezing (info 1), high body temperature (info 2) and pain over all the body (info 3) means you have the flu (objective). Here I present some well-known models:

o Linear regression – https://docs.aws.amazon.com/machine-learning/latest/dg/types-of-ml-models.html – It is good to work with number prediction. Examples: What will be the weather for tomorrow? For how much this house will be sold?

o Decision tree – https://www.ibm.com/support/knowledgecenter/en/SS3RA7_15.0.0/com.ibm.spss.modeler.help/nodes_treebuilding.htm – Find out the disease: are the sympthoms A, B and C true? Then disease X; Are the sumptoms A, B and D true? Then disease Y;

o Bayesian network – https://pt.slideshare.net/GiladBarkan/bayesian-belief-networks-for-dummies – When we have an evidence and want to reach its cause. Belief propagation. The same health scenario above can be applied, but in an inverse way. I have the flu. I must identify in this patient we have all the sympthoms, or even without showing sneezing, he still has the flu.

  • Models for unsupervised training

    It happens when you don’t have the conclusion the algorithm must reach. You will have to check it every time it runs. Example: if the customer bought product X and Y, he may be interested in product Z. You won’t know if it is true, because the customer may get interested, but even with that, don’t buy the product. Here I present some well-known models:

Association – https://en.wikipedia.org/wiki/Association_rule_learning – Same example above of suggesting things to be bought;

o Anomaly detection – Any chart control or information where anomalies have to be alerted. Stock market or the temperature inside a factory’s chamber, as instances;

  • Models for semi supervised training

When sometimes you know what you will reach. Your problem will set if you will be able to use this model. More models can be found at https://en.wikipedia.org/wiki/Outline_of_machine_learning#Machine_learning_algorithms

Configuring a model

It happens when you have a known model and must configure it. Sometimes you won’t have to train the model.

An example for linear regression, which came from another customer: he wanted to mix many different information from many different sources and reach out how it would affect their product pricing. For each of their products, you configure the algorithm in order to understand that supply A affects 10% of final product pricing, supply B affects 50%, and etc. Knowing that, the algorithm would be able to “predict” changes on their prices and warn them to buy more or less of each supply. This way they would be in front of their competitors, saving money at the right time;

And then… Training a model

Once you have a problem requiring a model to be trained to identify your target, you will have to have data to train your model. The image analysis that cloud providers provide through APIs are great examples. Once you upload an Eiffel Tower image there, the algorithm already knows there is an Eiffel Tower within your image. But how do they do that? They have already trained the model to understand patterns on the image and then classify it. It’s the same thing that Facebook does every time it recognizes faces on your uploaded photos. For the Facebook example, it gets even more impressive because Facebook trains their algorithm with everybody’s faces. Then they know that your image has a photo of your specific friend, and suggest you to tag that guy! It’s not just a generic person recognition like other models do.

 

How to do that?

At last, there are many tools, such as Google AutoML, Amazon Machine Learning, Watson and TensorFlow (open source tool). The providers solutions allow you to send a given model to cloud and then use their infrastructure to run, train and consume it;