Turn it overOperationThe light is close to the book, and there's not a lot of gold words left in my head, but there are a few analytical frameworks that do make things easier. After three years of grinding on the electrician's operational posts, from writing detailed pages to staring at the transformation funnel to the big drive, it was felt that it was working "with a hand." it's not until i read the book that i realizedIt's a sense of hand. It's a detachable logic behind itIt's just that no one helped me break that window paper。
What's the light of the operation
The book breaks down operations into lines of users, products, data, content, and each line is not the right "you gotta value xx" bullshit, but it's down to specific actions and indicators. Like whatUser operationsIt will enable you to divide the life cycle of the user into five phases, one that is new, activated, retained, cashed, recalled, with what strategy, what core indicators to measure, and very detailed. I looked at my background data all night。
I've done a lot of work before, and every time i write, "activities are working well. Next time, it's perfect."I don't even have a quantitative standard for "okay."What to optimize? It's the same as an eye-to-eye bump, a bag and a consolation saying, "experience is building."。
Is the light of operation worth reading
To be honest, this book is not the kind of guy that makes a good table. Words are flat, and some paragraphs smell like textbooks, and if you look at "subversive cognitive" pleasures, it's probably even. But if you're running a business, even after three months, those decomposition frames in the book can help you to put together a line of scattered and fragmented experiencesSaves at least six months to hit the south wallIt's a good deal. And then i adjusted my expectations to read it as a tool book and not as a novel, and it was completely different。
The two new people in the group, i had them flipped over, and the feedback was, "look, i finally know what's going on with the work every day." it's more useful than i thought, especially for people who just moved in。
How do you read the light of operation
Don't read it in one breath. I've done it three times: first reading the two chapters of the user and product, commenting on the start of the project; second eating of the data and content chapter, defining the indicators in the book as one by one, against the calibre on our bi board; third going to the case section, and then looking at how other people landed much faster, so many of the "yes" came out at this moment。
There's a little advice in the book that i've used repeatedly -- every chapter i've read, i've put on the last real project, and where i can't get it is where you really don't get it. It's a lot more than thinkingAt least it doesn't turn out to be a collectionI don't know. I'm still doing this stupid thing, but it does work。
After reading the memo that night, a short line was added: "lead the plan later, first, and make it clear which stage i want to solve. "that's all i've been looking at for weeks。
