Monday, 8 June 2015

NoSQL Matters??… Yes it does!!....

Reflecting on the 2015 Conference in Dublin….



Last week, after winning a free ticket in a competition from the *Hadoop User Group on meetup.com, I attended a NoSQL conference in Dublin and was fascinated by the progress in NoSQL technology, which was show cased on the day!

There were very strong presentations from VoltDB and ArangoDB.com showcasing their offerings in integration and multi-model NoSQL databases that set my mind alight with ideas and thoughts. Also of note was a presentation from Bit Expert’s “Stephan” on PostgresSQL and what it can do. It was an enlightening exploration of how JSON and NoSQL can play so well together!!

The concepts that were floated at the conference were all great but from what I have seen, the first prize goes to ArangoDB.com and their Multi-Model NoSQL database. The concept of having a database that is secure, can handle Key Value stores, documents stores and Blob storage on one database is most impressive indeed. The amount of coding in small to medium level project teams would be reduced along with design concepts like “micro-services” which augments functionality through the use of “Foxx” (JavaScript Framework, they use Node.js) to widen inbound data sources and thus the effectiveness of the application. To critically complete the evaluation, I would like to know more about the security aspects of the multi-model offering and also note that for large data modelling jobs, Hadoop would probably be a better solution. That said, ArangoDB.com have created a pioneering product that brings NoSQL technology to smaller projects that would traditionally have relied on relational databases. More information on my No. 1 presentation at: https://www.arangodb.com/foxx/.


 VoltDB had a strong presentation on database design and how VoltDB effectively streamlines important areas of network and database management under one roof where a solution currently could see numerous venders fulfilling different aspects of your relational and non relational database needs. I also had the pleasure of working briefly with the speaker Akmal Chaudhri in early 2000 whilst we both were at Informix Software and am glad to see the quality of his work is still exactingly high, which reflects in the very logical solution behind VoltDB’s offering. They say if you surround yourself with like-minded people, you can do great things. It certainly looks that way at VoltDB! They earned my No. 2 vote!

One other notable presentation is from Nathan Ford on monitoring and defect management, which is something Developers generally are not that fussed about. However, wearing my risk management hat, I think we Developers could be thinking more deeply about defect management and I love Nathan’s graph based defect management system for clusters that if developed further could be a real competitor for more developed systems like Prometheus. It’s efficient and with development continuing, a real winner for standard systems monitoring, unobtrusive defect capture and system behaviour analysis could surface in the not too distant future. Developers can gain a real insight into how their code behaves in a system (v design intent) and thus streamline their code for better efficacy and outcomes. Nathan’s talk and ideas earns him my No. 3 vote!


There was a diverse and interesting group of folks there from the NoSQL world to software nerds like myself to the Data Science world whom all agree that NoSQL does matter and despite what some folks say… it is here to stay! With the onset of new technologies that widen the scope of NoSQL, the technologies which streamline relational and non-relational databases into a single user friendly cluster application are here and will gain more and more acceptance in business when business fully realises their needs in diverse dataset management and/or big data analysis. A key indicator of this position is the adoption of NoSQL by key industry players like Microsoft and also Oracle who initially lobbied against NoSQL. The acceptance of NoSQL by key industry players like these is an important milestone in the lifecycle of NoSQL and with time, business will become more and more comfortable with it, when they see it does more then simply replicate the initial success of Google’s Big table.



For business in times to come, NoSQL could be the differentiating factor for their success against a competition that is tightly coupled with only SQL/relational database technology. Personally, I think this is not a question of “if”; it’s a question of “when”. Finding the fit for your network and database needs is not an easy task especially when the landscape is changing as hyper-connectivity increases and more and more competitive edge is driven by data science for business. Early adaptors in business given the technology’s stage in development should certainly be aware of NoSQL and plan for it’s incorporation into their digital footprint.  In my view, not evaluating NoSQL today in your business’s journey may cost you dearly tomorrow… the only way is to evaluate it and find out if there is a present or future need for NoSQL!!... The results just may surprise you! 

For more on the conference, visit NoSQL Matters website at https://2015.nosql-matters.org/dub/#home


Sources/Credits:

Pics;





Credits;


*Many thanks to Silviu and Uli from the Hadoop User Group for hosting the competition where I won the ticket to NoSQL Matters conference 2015. More on this key industry group at http://www.meetup.com/hadoop-user-group-ireland/

Monday, 1 June 2015

The Repeat Sale! Create value, not want!

Leaving convention aside for necessary Reinvention…


We all know the “Sales guy”, the guy who closes the deal and in the vacuum left by him is the memory of a charismatic fellow, who made us forget why we are doing business with the customer in the first place!!... Strange as it sounds, it’s a reality that often visits us too late when our customers are barking at us as to why they are leaving to find someone else who actually fulfils their needs and keeps all their promises!      

Leaving aside the ‘obvious’ clichés like “always keep your promises”, “say what you mean, mean what you say” and my personal favourite “do what you said you would do”, management over-focus on aggressive sales growth is often driven by variables outside of the company. I submit that this creates strategic weakness in how repeat customers are managed through Account Managers, whom are often conflicted in their roles by design.


In a prior role in Credit Management, I got an escalated account where a senior customer manager was very angry with what he saw as an appalling service provided by the company. The account was small in revenue terms and ”the sales guy” was happy for me to deal directly with the customer. After getting a raw deal from multiple departments, whom should have organised the resolution to the problem, it was passed from department to department as the customer grew more and more red faced! When I eventually got the call, he was furious and I certainly got a piece of his mind. Appalled, I worked through his issues after the initial venting; when a bad call was turned into an opportunity to “make it right”.

Here is what I did after the first call:
  • Confirmed customer allegations of overcharging
  • Responded to the customer with confirmation and a plan to put it right
  • Coordinated with all stakeholders to find out exactly what happened our side and obtained documentary evidence of transactions supporting the process flow that is in contention for the periods in question.
  • Conducted a forensic analysis of the documentary packet identifying bias errors in process flows; tracking them back to the teams and individuals concerned with the assistance of their team leaders.
  • Agreed a resolution with the team leader on training to fill the skills gap identified in the investigation and a timeline for completion of retrospective queries related to this issue.
  • Followed up with the team leader to confirm query resolution compliance, deployment of training with his team and brainstorm any automated enhancements that could prevent this happening again.
  • Updated the customer and asked to meet him face to face to discuss next steps.

 A busy man, the customer made time for me and I went out to see him. He was in a more positive mood given he signed off on numerous credit notes showing progress on my company’s part.  After that positive meeting, I did the following:
  • Updated all stakeholders involved on the meeting.
  • Followed up with internal stakeholders to put simple changes in place.
  • Confirmed deployment was successful with all teams in a feedback session
  • Trained my own team on the changes and what to look out for into the future.
  • Followed up with the Billing Queries Team Leader to confirm all queries resolved along with audit of subsequent bills confirming correct billing.
  • Updated the customer on the successful resolution asking for their feedback.
  • Set a review call for three months from that point to confirm account was running ok and to address any issues therein.

Sounds exhausting for a small money account, right? Well it was and with “the Sales guy” uninterested still, the happy customer who was impressed with us pushed within their company for a regional switch to my company which was a contract in the millions. Suddenly the uninterested Sales guy appeared along with a “Strategic Sales guy” who I never heard of before. Apparently, he has special talent that means a customer will never have to worry about a thing. All it took to get a multi million dollar contract was a great product, service offering AND a back office structure that minimises the customer’s cost of doing business in dollars and resource drain on all levels.


This true story shines a light on what so many overlook in the dogged chase of aggressive sales growth, which by its very definition is unsustainable. If you don’t consolidate your back office correctly with the customer at the centre of your efforts from employee incentives to organisational design, you will eventually loose your customers and not replace them fast enough to maintain your trajectory thus crashing your sales growth.

On that note, here is some advise I have for all who are thinking about this and how they could fix this issue within their company:
  • a)    Don’t assume your products are indefinitely loved by customers, incentivise your Account Managers to complete “routine check-in calls” with customers of all sizes finding out their current satisfaction with the company AND its products along with their needs going forward.
  • b)   If staff are incentivised on meeting sales targets that are crazy aggressive with no additional KPIs on customer care, then their anxiety in getting back to making money can come across as arrogance to a customer who spends small with the company. You never know who will grow into the titan of tomorrow, and if you treat everybody as the titan of today, tomorrow’s titans will remember you kindly.
  • c)    Today's big spend accounts needs to be handled by account managers with exactly the same high level of training as regular account managers, the only difference is they handle less accounts. Apply your teams expertise evenly remembering big spend accounts spend money to have a great product AND service, not to ensure your other customers don’t have the same experience.
  • d)   Create a KPI incentive base for account managers that are different to new business development executives who should be focused on business expansion plans only! Ensure your KPI suite for account managers covers non-sale check in calls, billing query resolution rates, customer satisfaction index surveys, sales (repeat) and sales (new product ranges). The account manager as part of the KPI incentive suite should do cross selling as the customer’s main point of contact.
  • e)    Conduct index surveys on account managers by internal stakeholders (ran by HR) to ascertain their level of skill in project management, stakeholder engagement and stakeholder influencing.



There are more, but even with these changes, the impacting and consequential changes needed to do it right would make a positive impact on the organisation in my view. It comes with risk, but doesn’t all great things come with risk before you can reap any reward? I think so, what do you think?



Sources/Credits:

Pics;



Credits: