The path to organization metrics collection
This Article I believe would be a place for me to document my data gathering obsession, I will be covering what I've seen working as a metrics collection method in different organizations and how effective the approach was from Technical and Business perspectives.
Need for data
It’s proven any business resolution and requirements should be backed by data. That’s why it’s essential that any organization has its very own data and metrics collection process, the one that will ensure the Technical is feeding the business interest.
Let’s take for instance a hypothetical example, let’s consider our fictional company which for some reason will be called: AcmeBank, this financial institution have of course many different layers, departments, projects, and of course teams.
You might ask why ? for that let me give you a hypothetical question :
How AcmeBank knows it’s the right time to expand to Singapore ?
The answer is what I love to call: Business Threshold, the continuous study of a market for our prestige bank will lead us to ask the following question :
1 — How many users do we’ve In Singapore?
2 — How many active users do we’ve in Singapore?
3 — how many transactions do we’ve on a daily basis on average in Singapore?
4 — How many new users do we’ve in the cycle in Singapore?
5 — Level of Customer support is being required to cover our lovely Singaporeans.
The past 5 questions are nothing but the starting point for our quest but can be good enough to determine how big or small the market is, as well as how important this market would be to us in case of investment.
you might ask now how we’re going to know that fact, the fun part starts from here as this is how I would decompose such a process :
1 — Decompose your terminals: How many terminals do you’ve, Web? Mobile? desktop ? all of them? this question will give us an idea about where we should inject our metrics collector.
2 — Get your Budget: This will make the whole difference, how much you’re willing to spend in such a process? facing any third-party system ? or do you want to go Solo?
3 — Understand your topology and define the central point of control: understanding how the Company data and conversation amongst each module is important, is your organization API Based? or Event-Based? as Metrics collection is a Heavy process. Failing to fully understand the different layers of your organization results in a failing of the whole process or worst, The corruption of data.
4 — I real Time important? : Knowing the difference between the two will make your life much easier, remember the above 👆 question.
To be continued …
