Worth collecting: 70 common mistakes in operations!

Introduction : Whether you are a newcomer or a veteran, I am afraid that everyone cannot avoid the 70 common mistakes in Internet operations . How to avoid such mistakes? The editor believes that other people’s experiences can be read and thought about repeatedly!

text

1. Basic operations

1. A table of people spent an afternoon thinking about a bad name

2. Post promotional posts on Tieba/Douban/QQ Space/WeChat Moments

3. Not actively looking for work to do, relying entirely on the boss to assign tasks, being lazy as long as possible

4. Engage in low-level repetitive labor for a long time and be satisfied with it

4. Lack of curiosity

5. I am not proficient in using any of Office, PS, Axure, MindManager, Markdown, Visio, and SPSS

2. Event Operation/Planning

6. Writing without considering product strategy

7. Doing activities for the sake of doing activities

8. Event planning is only written in Word

9. Assuming Users Are Stupid

10. Not testing the activity logic after writing it

11. Not considering the return logic after reverse/jump

12. No WiFi at the promotion site, asking users to download/register/scan the code

13. Not estimating campaign costs, conversion rates , and ROI

14. No maintenance of new users after the event

15. Self-indulgent promotional content

3. Market Operation/Channel/MKT

16. Branding without considering user attributes

17. Set KPIs based on your own ideas

18. Calculate channel effect by exposure

19. Trust Party B’s PPT

20. Not looking at channel data before launching

21. Change quantity at will

22. Randomly exchange friendly links

23. Failure to bind the channel statistics code before the launch.

24. Blindly trusting data

25. Blindly trust yourself

26. Blindly trust the channel

27. Pay for the packet loss rate of statistical tools

(IV) New media operation /community operation

28. Don’t use clickbait headlines

29. Buy a lot of fans

30. Believe that content is more important than channels

31. Not planning your content

32. Output content at random time

33. Ignore users

34. Typos

35. Colorful typography

36. Not maintaining users based on community pyramids

37. Worrying about users and spending a lot of energy solving their personal problems

38. No feedback on user opinions

39. Completely abandoning your work after get off work or on holiday

(V) Product Operation

40. Important web-based function entrances are hidden like Easter eggs

41. Unnecessary redirects on the web

42. App does not hide traffic

43. iOS launch expectations do not take into account review failures

44. Wasting time on Tier 3 and smaller markets

45. Not checking the market for duplicate names before naming your app

46. ​​Operations put forward requirements without considering the product iteration cycle

47. Fight with the product manager

48. Over-emphasizing user research

49. Substituting small samples for overall demand

50. Use the cheapest outsourcing

51. Make an App for a Web Framework

52. Sign-in/lottery/gift packs, tasks/daily/random push notifications, don’t use them if it’s not a game

53. Login/Log in, Wait/Later

54. Trying to use an app to bind the user's 24 hours

55. Over-pursuing product details when basic functions are not fully implemented

56. Using “craftsmanship” as an excuse for inefficiency

57. The beginner guide cannot be turned off

58. No mobile adaptation

59. Tell the designer to "make it more elegant and simple"

60. Tell the developers, “Here’s a button, here’s a feature, hurry up and make it so it’s ready for tomorrow.”

(VI) Others

61. Not asking the financial invoice type before issuing the invoice

62. Don’t go through the legal process before signing a contract

63. Plagiarism, not asking before plagiarism, not admitting after plagiarism

64. Not considering the consequences before doing things

65. Not reflecting on what happened afterward

66. Procrastination/shirking responsibility/lip service

67. Forcing promotion without money, resources, connections, or reputation

68. Complain about bad decisions after bad results come out. If you firmly believe that what you are doing is wrong, then don't do it.

69. Over-design, over-planning, over-optimism

Most Important

70. Low EQ/IQ