# From More to Fewer
By:: [[Ross Jackson]]
2022-10-29
In analysis, as with many other things, it can be challenging to know where to start. In terms of any given project, it is constructive to start with the direction and an interrogation of the problem. Determining the context is a good place to start. Understanding _what_ is being asked and _why_ it is being asked will allow an analyst to make strategic tradeoffs during the project.
As a rule, it is beneficial for analysts to have more than what they need. More data, more variables, more time – more is what allows an analyst to eventually be selective. This analytics-based selectivity is what allows an analyst to understand the value of what is being presented. If one intended to collect data from 1945 to the present but was only able to collect data as far back as 1970 for one of the variables, one examined the data from 1970 to the present. When a leader says “hey, 1970 seems somewhat arbitrary. Why did you select that year?”, the analyst will be able to say that is the furthest year back for a complete dataset. If one started with a 10-variable model, but through analysis found that a 3-variable model provides the same explanatory power more efficiently, one can communicate why “only 3 variables” were used in the model. Moving from more to fewer provides useful insight.
Moving from fewer to more is potentially never-ending. This type of situation frustrates organizational decision-makers as it seems that at each meeting the analyst has an excuse as to why additional time is needed to look at one more thing. Potentially, there is no end to such extensions. One more thing could always be analyzed.
Being an effective analyst requires that one become a strategic analyst. A minimum part of becoming a strategic analyst is to ensure that one understands what is being asked and why. Adopting the approach of moving from more to fewer (in terms of data, variables, and time) is beneficial for managing analytic projects and ensuring the final product can be delivered within the agreed-upon schedule, and that one can address questions related to the scoping of the project. Moving from more to fewer will result in more [[success]] and fewer headaches.
#### Related Items
[[Analytics]]
[[Problem Solving]]
[[Thinking]]
[[Understanding]]
[[Decision-making]]