It's been over a week since Jiang Yixin switched to product manager, but she still hasn't fully adapted.
Previously, the first thing I would do every morning when I got to my workstation and turned on my computer was to pull up the code, check if anyone had submitted any new changes the night before, and see if CI had been run. Everything was crystal clear; green meant it was correct, and red meant it was wrong.
Now, the first thing I do when I turn on my computer is to check Lark.
The top of the message list is always "Open Things User Feedback Group," with at least dozens of messages every morning. Some people say the onboarding page is too complicated; others post a screenshot and ask "Why isn't it moving?" but the screenshot doesn't show any information, just a blank screen.
When she first saw these messages, she thought that users didn't know how to use computers, so she should let them learn on their own. But after talking with Su Niannian, she had a new perspective: if users don't know how to use it, it's a problem with the product.
Lark gave a notification sound; Su Niannian had finished revising the draft product document she submitted yesterday and sent it back.
This was the first product module she was independently responsible for: the user onboarding process deployed independently by Open Things. It took her several days to write, and she believed it was very clear.
Open the document, and the screen is full of red annotations.
Thirteen articles.
Jiang Yixin took a deep breath and began to read through the messages one by one.
Su Niannian's annotations were densely packed, but they could be summarized into three layers.
The first layer is formatting. Jiang Yixin's product documentation reads too much like technical documentation, for example. "Call the OAuth 2.0 interface to obtain a token and complete the cloud account authorization binding." Su Niannian changed it to. "Click 'One-click Binding,' which will redirect to the authorization page. After confirmation, it will automatically redirect back to the Open Things deployment page, and the deployment button will become available." Comment: "Users do not need to know what OAuth is."
This part is the easiest to change; it's just a matter of rephrasing it—maybe?
The second layer is the thought process. Su Niannian drew a large, bold question mark next to "Requirement Background": "Why do users want to deploy independently?"
Jiang Yixin's original text stated that "shared deployments present stability and isolation issues."
Su Niannian's annotation. "Users don't know what shared deployment is. They only know 'The thing I spent time making suddenly can't be opened.' What they want isn't isolation, but a sense of security, 'What I made is mine, it won't suddenly disappear.'"
Jiang Yixin stared at this annotation for a long time.
The third layer is abnormal scenarios. Her product documentation only outlined the normal path: successful binding, deployment complete, everything goes smoothly; binding fails, start over. Su Niannian added a sentence at the end of the documentation, "What if the balance is insufficient? What if the key is entered incorrectly? What if the region is selected incorrectly? What if there is a cloud failure after successful binding? The normal path is just the foundation; the abnormal path is where the value lies."
The final comment summarizes. "A product is a higher-level abstraction of implementation. The format of product documentation is minor; the two truly difficult things are identifying unspoken user needs and making the right decisions."
Jiang Yixin read the sentence aloud twice, then copied it into her notes.
She thought switching to product management was just about changing the document format, but Su Niannian meant changing the way of thinking.
In the past, when writing code, right was right and wrong was wrong; the compiler didn't lie. Now, when making products, there's no compiler, only users. And users won't tell you what they really want, because often they themselves don't know what they want.
Jiang Yixin spent the whole morning revising the product documentation from scratch. She changed the requirement background to user language, added eight abnormal scenarios, and redrawn the onboarding process.
After making the changes, Jiang Yixin sent the new version to Su Niannian. Ten minutes later, Su Niannian replied with two small annotations, and the long red paragraphs were gone.
Jiang Yixin took the second version to the development team for a technical feasibility review. This was a new process that only started after Shen Congyun arrived. Previously, when Su Niannian made a request, the development team would immediately begin implementation.
After the Series A expansion, Open Things's technical team gained nearly ten people, with the most recent hires having been here for over a week. Among them, Jiang Yixin is most familiar with two.
Team leader Liang Wei, 42 years old, is a backend architect. Source Code was previously a backend architect in Kunlun Payment's department, but he was laid off due to "organizational optimization." Shen Congyun recruited him through his connections. He is quiet and doesn't talk much, but he quickly established himself as a technical authority in the team. There are no personal belongings on his workstation except for a thermos.
Qian Xiaole, 24 years old, with one year of experience, is a top student who graduated from Shuimu University. Her previous company was a large-scale startup in Beijing, but it went bankrupt last year due to funding shortages. She then returned to her hometown of Haicheng to find a job. She is lively and asks many questions. During lunchtime, she usually eats sandwiches and browses Little Red Book at her workstation, but sometimes she joins Jiang Yixin and Li Ting's lunch team in the operations department.
Jiang Yixin walked to Liang Wei's workstation and sent the product document sharing link to Lark.
"Brother Liang, this is the product documentation for Open Things's independent deployment guide. Could you take a look and see if there are any technical issues?"
Liang Wei took off his noise-canceling headphones and opened the document. He read it very quickly, finishing it in just over two minutes. Then, pointing to a section, he asked, "After independent deployment, how do we migrate user data from the Open Things repository to the user's own cloud database? Is it created as an empty file, or are the table structure and data copied over?"
Jiang Yixin.
"Old Chen handled a similar scenario before when he was doing modular decomposition on the BugKiller engine, and the data export used incremental snapshot mode."
She bent down, opened the code repository, quickly found the file path, and pointed to the screen: "This snapshot -e"
The core logic of the port module is here; you can refer to this pattern for your data migration layer.
Qian Xiaole, sitting at the next workstation, gaped and turned to Liang Wei, whispering, "Isn't she a product?"
Liang Wei didn't look up. "It's a good thing that a product manager can understand code."
Jiang Yixin heard it.
She did naturally start flipping through the code just now, but she didn't feel bad about it. She didn't switch to product management because she was "not suited to coding"; she just could do more things.
The technical review continues. Liang Wei said that the core logic of data migration is not complicated, but the difficulty lies in the differences in APIs among different cloud vendors. Qingyue Cloud, Tianshu Cloud, and Kunlun Cloud each have their own specifications, and the workload for adaptation is considerable. Although the first phase only requires adaptation to Qingyue Cloud, the amount of repetitive work in the future will be significant.
Jiang Yixin suddenly had an idea. "Should I include the requirements for an abstract adaptation layer in my product documentation? That way, developers won't have to worry about which cloud provider is behind it."
Liang Wei nodded. "That would be great." Then he shook his head, "It should probably be in the technical design documents."
Jiang Yixin's first collaboration with the product team was quite successful; they were on the same wavelength, which was completely different from what was said online.
Qian Xiaole was taking notes beside her, but after writing half a page, she realized she wasn't keeping up. She secretly Sharingan to the bottom of Jiang Yixin's product document, to the section on requirements and background, and activated her Sharingan! Copy! Paste!
At noon, Su Niannian passed by Jiang Yixin's workstation. "Xiao Jiang, want to have lunch together? We can also chat about the progress of the independent deployment, and let Boss Han treat us."
Jiang Yixin glanced at Li Ting lowered her head and pretended to be looking at the computer, seemingly unaware of what had happened.
Jiang Yixin embarrassed to refuse, so she silently followed.
Arriving at a commercial complex near the company, Han Luyi, Su Niannian, and Jiang Yixin went into a steamed dish restaurant.
While ordering food, Jiang Yixin listened and took notes: Teacher Han likes sweet food, and Teacher Su likes spicy food. Quietly remembering other people's preferences is Jiang Yixin's little social secret; the next time she shows it, the other person will feel valued.
While waiting for the food, Su Niannian asked Jiang Yixin how her experience was after the job transfer. Jiang Yixin said it was pretty good, and then began to report on her work progress. She had finished revising the last two suggestions in the product document, discussed the technical review with Liang Wei, and it had been preliminarily approved. Su Niannian nodded in satisfaction.
Then Han Luyi asked a question, "After a user binds their cloud account, if there's a problem with the cloud service provider, such as the regional outage that Qingyue Cloud experienced last time—what will the user see?"
Jiang Yixin silently breathed a sigh of relief. She had only written "binding successful" and "binding failed" statuses in the product documentation and hadn't considered the scenario of "cloud problems after successful binding." However, after Su Niannian gave feedback that morning, she added the exception scenarios, which happened to include the one she had just encountered.
Users will see pre-categorized error messages: whether it's a problem with the Open Things Server, the cloud service provider, or the client.
Han Luyi nodded. "The design is good."
"A core selling point of independent deployment is transparency," Su Niannian added. "If your app goes down, at least you can see whether it's a cloud problem or a code problem. Users will only trust you if it's not a black box."
Han Luyi and Su Niannian went back and forth, discussing everything from anomaly alert solutions to monitoring panel design, from technical architecture to user psychology, their conversation moving at a pace reminiscent of a game of billiards.
Jiang Yixin turned her head back and forth following the sound of the voice.
The interaction between Teacher Han and Teacher Su was so natural.
Back at her workstation, Jiang Yixin took out her phone.
[Xiao Jiang (Product Version)]: Big Liu, do you think it's okay for a CEO and a VP to date?
[Big Liu]:???
[Big Liu]: What shocking news is this? Tell me about it!
[Xiao Jiang (Product Version)]: It's okay, it's just a little bumpy.
[Big Liu]: ---- Jiang Yixin, shipping everything will only ruin you! Delete the chat history now!
Jiang Yixin deleted the chat history and chuckled to herself.
Gossiping about the boss during work hours is a bit exciting, not good.
Then I thought again, it doesn't affect my work, so it's fine.
Around 5 PM, Jiang Yixin went through the product document from beginning to end, finalized the last few revisions, and sent the final version to the Lark product group @Su Niannian.
Qian Xiaole has already left; she's the type who leaves work on time. Liang Wei is still here, wearing headphones and coding; he seems like the type who works late into the night.
Jiang Yixin packed her things to leave, passing by Liang Wei's workstation.
"Brother Liang, the final version of the product documentation is out. I'll go through it with you again tomorrow."
Liang Wei took off one earphone. "Okay."
Jiang Yixin hesitated for a moment. "Brother Liang, can I ask you a question?"
"You ask."
What was it like working at a large company—specifically, dealing with Source Code?
Liang Wei took off his headphones and sighed.
"I've been in this industry for almost twenty years. Because of age restrictions, I went back to the job market and sent out a lot of resumes, but the big companies didn't even look at them. A few small companies did respond, but the salaries were halved. During the interviews, I could tell that they just wanted cheap and easy-to-use cogs in the machine."
He unscrewed the thermos and took a sip.
"When Boss Han interviewed me, he asked me, 'What do you want to do with the Source Code?'"
He closed his eyes.
It's not "What can you do?", it's "What do you want to do?" It's been a long time since anyone asked that.
Jiang Yixin recalled that conversation; Han Luyi had said something similar to her, "Just figure out what you want to do in the Source Code yourself."
She didn't understand it then, but now it seems like she has some answers.
"Go home early." Liang Wei put his headphones back on.
Jiang Yixin walked to the elevator and glanced at Lark.
Su Niannian gave the product document a thumbs up, but made no new comments.
Jiang Yixin smiled.
The elevator doors opened, she stepped inside, and pressed the button for the first floor.
Let me browse through Little Red Book again.
The third post on the homepage is from a user who runs a baking studio. The post includes a picture of a blank error page. "The reservation system I used, which I made with Open Things, suddenly stopped working for a few minutes this afternoon. My customers were waiting to pick up their cakes. I called them and found out it was Server issue. It's back up now, but I'm still a little panicked. Has anyone else experienced the same thing?"
The top-voted comment among the dozens of comments reads, "That's why this kind of thing can't be used for legitimate business."
Jiang Yixin stared at the screen as the elevator arrived at the first floor.
She added it to her favorites, took a screenshot, and then stepped out of the elevator.