Looking for roles centered on research, analysis, and structured thinking.
A dashboard that maps the team's technical skills and individual traits alongside how the company's systems actually connect — current pain points, proposed fixes, and where the org is heading. The point is to make the next conversation focused, and to give everyone a shared anchor to come back to.
Read the notesOur team had three quiet pain points: sales pipeline numbers were still being counted by hand, no one could see how things progressed once a deal became a project, and resource allocation lived in someone's head — so projects slipped without anyone noticing in time. I designed and shipped a system that threads sales, project tracking, and finance into one shared workflow, so the next conversation is about the same picture.
Read the notes
The observability half of the PMS story: a pipeline where production failures file their own issues, evidence attached — 64 errors auto-captured in the first 18 days, 94% closed, median fix time about five hours. Bug reporting stopped being the user's job.
Read the notesTurns 20 messy research tabs into a tagged, exportable workspace. Highlight on any page, tag, compare across sources, export to Markdown.
Read the notesMost factory work instructions are dense single-sheet tables that operators stop reading after the first day. I rebuilt one as a step-by-step visual flow — fewer fields, clearer hierarchy, the same information made actually usable on the line.
Read the notesSeveral years in digital transformation and project management — I'm the kind of person who breaks fuzzy requirements into clear steps, and a cross-domain learner by habit.
• Curious about how the tech industry actually moves; I read industry news, research reports, and a wide range of books (Improv Wisdom, The Republic of Tech, The Psychology of Money, The Inevitable, and others).
• My working style leans toward deep work, independent delivery, and producing structure, writing, and diagrams as the actual output.