EDISON / FDE FIELD NOTES
See the workbefore you design the system.
I work with manufacturing and operations teams to uncover the real problem, define the smallest useful change, and carry it through to adoption.These notes show how problems surface, how people agree on a change, and whether the result becomes part of everyday work.
Chinese + English · Updated regularly · RSS
RECENT / LATEST
Latest notes and cases
Each piece starts with a real workflow, decision, or project stage—and separates what happened from what remains unproven.
What I Look For When No One Has Asked for a New System
Some work gets done every day only because someone patches the process by hand. A lack of complaints does not mean the process is working well.
How We Turned WeChat Factory Reports into a Daily Operations Report
The company did not ask for a new system. I noticed two clerks rebuilding the same records every day, while the same production data had to be reshaped for separate reports.
Connecting a Manufacturer’s Website, Inquiries, and Internal Follow-up
A website was only the entry point. Buyer conversations could move forward only when the company could support them with accurate product information, import requirements, and quotations.
Connecting a Manufacturer's English Website, Video and Publishing Workflow
The project did not begin with a list of AI tools. The company did not yet have a repeatable process for producing English content.
What I Check Before a Business Website Goes Live
A working URL only proves that the site was deployed. Product claims, mobile usability, crawlability, and the buyer’s next step all need separate checks.
TOPICS / RECURRING QUESTIONS
Four questions I keep returning to
They all ask the same practical question: how do you turn an unclear business problem into a change people will actually use?
Problems no one has named yet
When a workaround has become normal, how do you decide whether it is worth fixing?
↗02AI in an existing workflow
Start with the step that keeps failing, not a catalog of new tools.
↗03Factory data people can use
Connect shop-floor input, calculation rules, and the reports managers use.
↗04Turning export inquiries into an internal process
Keep the website, buyer conversations, and internal product information consistent.
↗CASES / PROJECT NOTES
What happened, what changed, what remains open
These are not victory stories. Each record explains the setting, the decision, who had to be involved, and where the work stood on the date shown.
Turning WeChat reports into usable factory data
- Context
- More than one hundred workers reported production output in WeChat groups while two clerks consolidated the records by hand.
- Choice
- Keep WeChat as the shop-floor input and handle parsing, review, and aggregation behind the scenes.
- State
- The first version produced a working daily report; the same data was then used for capacity, exception, and finance reports.
Building a manufacturer’s export workflow from scratch
- Context
- The manufacturer had products and capacity but no connected export workflow.
- Choice
- Connect market research, the website, Meta, WhatsApp, and internal follow-up.
- State
- Across separate inquiries, next steps included product matching, sample requests, sending technical documents or proposals, and quotation discussions.
A manufacturer’s English-content workflow
- Context
- A manufacturer lacked a dependable English website and video-publishing workflow.
- Choice
- Confirm product facts first, then use HeyGen and n8n to automate repeatable production and publishing steps.
- State
- The English website is public. HeyGen and n8n were used for video production and publishing steps, with final publication kept under human review; search figures are reported only as dated snapshots.
ABOUT / EDISON
I write about technology—and the operational work that makes it useful.
I started in enterprise backend development, moved into customer-facing delivery, and later worked on a solar-energy venture. I now work across factory digitization and export operations for manufacturers. This site is organized by problems and decisions, not as a career timeline.
Why this site exists ↗How I approach an operating problem
Start with how the work gets done today
- 01Find the steps that still depend on repeated manual fixes
- 02Ask business owners, frontline teams, and engineers to walk me through the rules they actually use
- 03Choose the smallest change people can adopt without disrupting the work
- 04Stay until the first useful version becomes part of the daily workflow
WORK WITH EDISON
Is your team still holding a process together with manual workarounds?
Start with the operating context: how the work is done today, where it breaks down, and who is affected. Then we can decide whether the problem is worth solving—and whether it needs a project.
Start with one real problem ↘