Client work through InsideBoard
Automating coaching and improvement programmes
Managers and trainers submit one form. Feedback, scores and tracking reach the right profile without anyone copying them across.
I work with clients to understand how their programmes run, challenge requirements and turn them into InsideBoard configuration and automation.
Forward Deployed Engineer, InsideBoard AI · July 2026 to present · Enterprise SaaS, people development
A form is submitted
A manager or trainer submits feedback for a person or team.
The workflow applies the rules
The workflow identifies the recipient, computes the relevant result and prepares the profile update.
The profile and tracking are updated
Feedback, scores and programme tracking are written to the relevant views.
Overview of the documented coaching workflows. The exact scoring and visibility rules depend on the programme.
The problem
The outcome
My contribution
The specifics
- Forms connected to profiles, scores and KPIs through automation and native configuration
- Field coaching: feedback appears on each coached person's profile, checked across all 123 people in scope
- New-hire training: daily feedback, quiz score and certification decision gathered in one view per trainee, with clearly labelled AI readiness briefs for trainers
- Improvement plans: site diagnostic scores computed and checked in the platform, with manager-only visibility configured
How it works
- Workflows rebuild each profile section in full on every run, so late or repeated submissions never overwrite each other
- A scoring bug in a live programme was traced to its root cause, fixed and backfilled for all 17 affected trainees, after explicit sign-off
- Daily KPI jobs measure the delay between a field visit and its feedback, and count feedbacks per manager once per person and visit
- The next form is pre-filled with the latest feedback, looked up by visit date, so managers start from the current state
- AI briefs are optional by design: if the model call fails, the section is still written without them
Safeguards and quality
- Client discussions become business rules, explicit decisions and a written solution brief that guides implementation
- Each programme has its own repository with one status record, dated evidence and a gate that blocks changes to live systems until they are approved
- Reusable platform knowledge is collected into a shared knowledge base, and boundary checks stop one client's data from reaching another client's project
- Native configuration first: automation is added only where the platform cannot do the job itself
Stack
- n8n
- InsideBoard API
- InsideBoard Forms
- Paperform
- LiteLLM
- Fathom
- Claude Code
- GitLab CI