Practice: wa focus of e-commerce Operation Optimization

1. First of all, I personally think that e-commerce companies should set up jobs in WA. The level of recruitment is good or bad. Let's look at Ga and make the simplest qualitative analysis, I often say to my colleagues that "from nothing to existence" is a leap, and "from existence to good" is another leap. Your Wa Team is actually the same.
2. You have to know what your wa staff are doing to prevent your wa staff from becoming vase or a black pot, don't look at what people are doing when they are idle. In my opinion, WA and architects are a type of position, with more thinking than doing it. Ta's specific work is nothing more than the following:
Transform the requirements at the business layer into a complete metrics (metrics) System
Communicate with the technical staff to ensure that these metrics are effectively obtained and the systemic error is within the acceptable range.
Pass these metrics to related parties (sales, OPS, etc.) in a form that is easy to understand/spread (such as various custom chart interfaces)
3. In the early stage of e-commerce website launch (within one year), small-scale and frequently-used qualitative analysis is not required to complete the system, but to discover problems (or even not necessarily require solutions ); after the amount is reached, we will perform a large-scale quantitative analysis with less frequency to develop a KPI system for the operation.
4. In a single sentence, do not give command to WA Last but not least. I personally observe that e-commerce companies with Internet origins are still able to talk on one channel; it is easy for traditional industries to get involved. The final result is probably that wa staff are forced to provide reports on the cloud or without any means to harm themselves for data purposes.