Skills
What you can ask about, and how far I stay involved
From clarifying the issue through execution and operations.
I work as a Technical PM between business and production / engineering, and keep the project moving.
I do not build the request as-is.
I clarify purpose, context, and constraints,
then shape a structure the team can actually run.
For research, structure, and technical checks I also use tools such as ChatGPT, Cursor, and NotebookLM, and aim for a way of working that can be repeated.
Typical requests When to reach out
These are the situations where people most often ask for help structuring the work.
We want to renew the website, but we don't know where to start
- There is intent, but it is not structured enough to brief a production company
- It is hard to judge which company to ask, and how
We want to judge whether a production-company or SEO proposal holds up
- Priorities and intent in the proposal are not structured
- Reports arrive, but the next action is unclear
We need help structuring technical decisions and production progress
- CMS choice and structure are hard to judge
- There is no one standing between production and the business
We want to sort out the project as a whole
- Handover and documentation are thin, so the current state is unclear
- Specs and shared understanding are not structured internally
How I join a project How I work
I stay with the web project from the first conversation through post-launch improvement.
Planning
Clarify the purpose
Requirements
Share what decisions need
Design
IA, UI, CMS
Build
Implementation and adjustment
Launch
Release decisions
Improve
Measurement and operations
I take on the roles the situation needs
What I do What I do
I work across areas depending on the project, rather than staying inside a job title.
Issue-finding and requirements
- Interviews and structuring the issue
- Requirements, constraints, and priority
- Support for shared agreement
- Turning the brief into language a production company can use
Information architecture and wireframes
- Sitemap and path design
- Wireframes
- Content structure
- Design that assumes CMS updates
UI design and communication
- Layout and message structure
- Bridging design and implementation
- LP and owned-media improvement proposals
- Explanation and coordination with stakeholders
CMS build and front-end implementation
- WordPress theme work (ACF, templates)
- HubSpot CMS (modules, HubL)
- Adjusting existing CMS such as Movable Type
- Technical coordination with the implementation team
Analysis, improvement, and operations
- GA4 and Search Console analysis
- GTM and measurement design
- Conversion paths and content improvement
- Designing a repeatable improvement cycle
Scroll sideways to see other areas
Tools and techniques in use Skill & Tools
A reference list of tools and techniques I use depending on the project.
Planning / Direction
- Requirements / information architecture (IA)
- Wireframes
- Production progress
- Backlog operations design
- Client and production-company coordination
- Technical requirements
- SEO structure improvement
Frontend / CMS
- HTML5 / CSS3 / SCSS (Sass)
- JavaScript / jQuery
- WordPress (theme work / ACF / functions.php)
- HubSpot CMS (module development / HubL / fields.json)
- Movable Type
- EC-CUBE
- Git / GitHub
- Docker / Gulp
Analytics / Optimization
- GA4 / Search Console
- Google Tag Manager (GTM)
- PageSpeed Insights
- Looker Studio
- A/B test design
- Conversion-path improvement
Design
- Figma
- Photoshop / Illustrator / XD
- Canva
CRM / Marketing
- Salesforce
- Engagement Studio (formerly Pardot)
- MailPublisher
AI / Workflow
- ChatGPT
- Cursor (VS Code)
- NotebookLM
- Google Apps Script (GAS)
- Office365 / Google Workspace