The Work Projects Results FAQ About Book a Call
Instructional Design, Built in Code

Information alone does not change
how learners perform.

Tell me who you are, and I'll show you what's relevant to your situation.

I am

Prefer to send a message instead?

Is this your situation?

What problems are you
hoping to solve?

Static courses break student engagement and kill learning outcomes. By building natively in code, I deliver environments with built-in WCAG accessibility that never breaks, feeding real-time performance data straight into your LMS gradebook via SCORM and xAPI.

01

"Social media and AI have changed how students absorb information. The course has not changed with it."

The same student who cannot focus through a 40-minute lecture will spend three hours going down a YouTube rabbit hole. Attention is not the problem. The design is.

02

"Most courses are still built for the reader who takes notes and finishes every page. That's one kind of learner in a room full of different ones."

Readers, watchers, and doers are all in the same room. When the path through the material only works for one type, the others quietly fall behind.

03

"You added a tool. Students treated it like optional extra credit."

When the experience lives outside the course, students leave it outside the course. The solution was never another tab.

I engineer custom browser-based simulations, bypassing generic authoring tool limits. By wrapping the mechanics entirely around your specific performance gaps, I ensure skills are mastered, not just clicked past.

01

"Employees complete the training. Nothing changes on the floor."

Completion and retention are two different outcomes. When training doesn't explain why it matters to the specific person taking it, the click-through becomes a ritual rather than a learning experience.

02

"Mandatory training is the room nobody wants to be in. The phone comes out within minutes."

When the material has no face and no consequence, employees process it on autopilot. The quiz gets retaken until the passing score appears. Nothing sticks.

03

"We bought a learning platform. Our L&D team spent more time managing it than designing for it."

External platforms create overhead. Integration issues, licensing negotiations, and adoption friction often consume more resources than the training itself delivers.

Here's how I design for it.

01
Built for retention
Every activity teaches or reinforces something text alone can't.
02
Built to be finished
The goal is creating content where skipping ahead feels like a loss to the learner.
03
Built with code
HTML, CSS, and JavaScript are the foundations every LMS runs on. Build in that language directly and the result runs anywhere, with none of an authoring tool's creative limits.
Performance data

What changes when the design
is treated as seriously as the content.

Program completion
~60%
Cohort 1 to cohort 2, same instructors and course length. Replaced a paid third-party platform with coding practice built natively into the LMS.
↑ Hiring managers cited stronger technical readiness
Completion, free program
66%
No incentive tied to finishing. Built on the same design principles proven in the redesign above.
↑ Zero completion incentive required
New infrastructure required
$0
I build everything myself and deploy it directly into the platform you already run.
↑ No IT security review needed
"

When we moved awayfrom DataCamp, the obvious next step was picking up another paid tool. Coddy was on the table at five dollars a seat. Turned out we didn't need to look anywhere else. The same functionality got built directly into our own LMS, and I didn't know that was even possible.

Director of Training · Cybersecurity & AI Program
What I build

A friction-free experience,
built directly inside the platform you already run.

I turn static curriculum into interactive browser simulations; engineered using HTML, CSS & Javascript, all content is WCAG compliance and has SCORM or xAPI gradebook syncing.

A Tenneri-built course module
yourschool.lms.com / ACCT101 / Week-6
ACCT 101, Week 6: Debits & Credits
Overview
Activities
Progress
Module progress
60%
🎬
Concept Overview
Short-form summary · For every learner type
✓ Done
📊
Journal Entry Scenario Lab
Simulation · Decision-based · Self-paced
Live
🧩
Debit or Credit? Challenge
Game · Instant reinforcement
Unlocked
📋
Knowledge Check
Scored · Auto-syncs to gradebook
Next
🎬
Concept Overview
3 minutes · Video + text summary
✓ Done

A condensed walkthrough for the learner who absorbs by watching. No prior knowledge assumed.

📊
Journal Entry Scenario Lab
15-20 minutes · Hands-on simulation
Live

Learners work through a real scenario before assessment. Decisions have consequences. Wrong entries show the downstream effect.

🧩
Debit or Credit? Challenge
5 minutes · Game · Repeatable
Unlocked

Reinforcement that doesn't feel like repetition. Learners replay voluntarily.

📋
Knowledge Check
10 questions · Gradebook sync
Next

Scores sync automatically. No manual entry. Unlocks once the scenario lab is complete.

60% complete
Module progress
2 of 4 activities complete. On track for Friday's deadline.
Concept OverviewDone
Journal Entry Scenario LabIn progress
Debit or Credit? ChallengeUnlocked
Knowledge CheckLocked
Continue: Journal Entry Scenario Lab
Module in motion
Watch in full view
Module Architecture and Course Structure. Tabbed layouts, embedded activities, and interactive content living inside a single course page. No external platforms, no additional logins, no infrastructure.

There is more where that came from

Simulated OS Environment
Cybersecurity · Technical Training
Adaptive Assignments
Assessment · Gradebook Integration
Custom LMS Applications
Training · Phishing Simulation
Games & Gamification
Engagement · Voluntary Completion
Results in the wild

Three different problems.
One consistent outcome.

Learners who finished. Learners who wanted more. Learners who forgot they didn't want to be there.

Higher Education · Data Science
~60%
Completion increase
cohort 1 to cohort 2
Retired
Third-party coding
platform

When the redesign outlasted the vendor

The needPart of the course ran on a paid third-party coding platform. Students often stayed there instead of coming back to the main course, and completion in the first cohort reflected it.

Cohort 2 was redesigned directly from cohort 1's feedback. Coding practice moved off the third-party platform and was rebuilt natively inside the LMS, with the same instructors and course length held constant. Completion rose by roughly 60 percent. Hiring managers who later took on graduates from the redesigned cohort independently reported they arrived more technically ready, and specifically noted that students kept using the tool itself after the course ended, simply because they found it useful. Several students who had struggled with the first version came back in cohort 3 as QA testers, and said concepts they were now meeting elsewhere felt easier to follow here than where they'd first learned them.

"I must say this version was much, much better compared to the first." A learner · Data Science Program · second attempt after redesign
Higher Education · Emerging Technology
Asked for
more
End-of-course
learner response
66%
Completion, free
program

Making the unintuitive feel inevitable

The needA quantum computing course where the material itself was never the real problem. The challenge was sequence and analogy: keeping a genuinely difficult subject from losing the learner in the first ten minutes.

Every concept was built directly on the one before it, developed alongside subject matter experts who caught anything introduced too soon. Difficult ideas moved through analogy, application, and scenario in that order, so learners hit recognition instead of confusion. The real constraint was the sequence, not the subject. It ran free to attend with no incentive tied to finishing, and still saw two out of three learners complete it.

"When is the next one? I want to keep going." Multiple learners · end-of-course feedback
Corporate · Mandatory Compliance
<60%
Completion before
redesign
>90%
Completion after
redesign

The room nobody wants to be in

The needMandatory GRC and compliance training that employees clicked through on autopilot. The missing piece was relevance: nobody had connected the policy to what could actually happen to that employee.

The redesign led with the personal why: what happens to this specific role in this specific scenario if this goes wrong. Scenario-based modules put employees inside real situations, mapped to GDPR, SOC 2, and ISO 27001 frameworks. People stopped going through the motions and started paying attention.

"I actually understood why we have these policies. I had been clicking through that training for three years and this is the first time it made sense." An employee · Systems Training Coordinator · Compliance Redesign
Before you reach out

What is the first thing
holding you back?

Select what resonates and I will surface the answer that matters to your situation.

What is your biggest concern about a project like this?

On ownership
You own it completely. Every file is delivered in standard web formats your LMS administrator can open, edit, and maintain independently. No proprietary format, no locked system, no ongoing dependency. You get a permanent institutional asset, not a vendor relationship.
On your team's workload
Less than you expect. Subject matter experts provide the knowledge and the learning outcomes. I handle the instructional engineering, the activity design, the sequencing, and the build. Most engagements require a few focused conversations, not sustained time commitments. Your faculty or L&D team are the source material, not the project managers.
On investment
Projects scale with scope. The 20-minute call exists specifically to scope what makes sense before any figure is discussed. You'll know exactly what gets built, what it costs, and what your learners will experience before any commitment is made. No retainers, no surprise add-ons, no ongoing licensing.
On evaluating without committing
Several builds are live on the projects page, including the AI Communication module and the SIEM breach investigation lab. No login, no form, no commitment. You can also read a shareable overview, formatted for forwarding to a dean or an L&D director. Or reach me at ramano@tenneri.com. No pitch, no pressure.
You own it completely. Every file is delivered in standard web formats your LMS administrator can open, edit, and maintain independently. There is no proprietary format, no locked system, no ongoing dependency. A platform update won't break a native build the way it might break an external integration, because the code lives inside your system rather than calling out to mine. You get a permanent asset, not a vendor relationship.
Less than a platform dependency does. Nothing in a native build calls out to an external vendor's server, so there is no third-party update that can break it overnight and no license renewal that quietly changes what you have access to. It is stable at launch and sandboxed by design, which is also a security advantage. Once a build is configured for a cohort, it stays configured. The same lab can run every semester without being rebuilt. And because the logic is written from scratch rather than assembled from a template, things like rotating scenarios or randomized variables can be built in from day one, so a student who retakes the same lab three times gets three different versions of it, which most authoring tools cannot do out of the box.
Less than you might expect. Subject matter experts provide the knowledge and the learning outcomes. I handle the instructional engineering, the activity design, the sequencing, and the build. Most engagements require a few focused conversations rather than sustained time commitments. Your people are the source material, not the project managers.
Projects scale with scope. A single module redesign and a full program build are different conversations with different numbers. The 20-minute call exists specifically to scope what makes sense before any figure is discussed. You'll know exactly what gets built, what it costs, and what your learners will experience before any commitment is made. No retainers, no surprise add-ons, no ongoing licensing.
Yes. Several builds are live and fully interactive on the projects page, including the AI Communication module and the SIEM breach investigation lab. No login, no form, no commitment. You can also read a shareable overview, a clean document you can forward to whoever needs to see it. Or send a question directly to ramano@tenneri.com.
Need something to share with a dean or an L&D director? Here it is.
View & Download Overview →
Ramano Stoute, Founder of Tenneri
Ramano Stoute
Founder & Principal ID
Meet the team

The people behind
every build.

Ramano Stoute
Owns the instructional strategy on every project: needs analysis, learning objectives, sequencing, and assessment design.

I come from a family of educators, and teaching was always the assumption in my household. What I never inherited was a set of principles. Everything I built early on was intuitive, driven by wanting the process itself to be enjoyable, regardless of the subject.

That intuition started with being a student who hated cookie cutter courses, the ones where the summary at the end told you everything you needed and the rest was safe to skip. I design against that instinct in every build I ship.

The moment this became more than a personal habit: a program I redesigned saw completion rise by roughly 60 percent between cohorts, and the paid third-party platform it once depended on got retired entirely. The content stayed mostly the same. The design did not. That is when Tenneri became something I could offer other people, not just something I built for myself.

The methodology behind that habit has held up outside my own projects too. A Fortune 100 company took it through final round interviews for a Senior Instructional Designer role and made an offer. Their Group Manager of Learning Strategy and Experience Design and Senior Manager of Learning Development both flagged the depth of the process as the reason. Unfortunately, circumstances on my end meant I could not accept.

Ramano Stoute
Founder, Tenneri  ·  Instructional Designer and eLearning Developer
How it works

Three steps. No guesswork.

What happens after you reach out. Before any proposal, any contract, or any commitment.

Step 01 💬

You tell me what's not working.

A 20-minute conversation where I listen to what your program or organization needs.

Step 02 💡

I show you what's possible.

Inside the system you already have. No new tools, no new infrastructure, no new budget line.

Step 03 🛠️

We scope the first build together.

You'll know exactly what gets built, what it costs, and what your learners will experience before anything is agreed.

"

I caught myself checking my privacy settings on the way home. This is the first time the training stayed with me outside of work.

Marketing Associate · Cyber Awareness Program

Let's make your learners feel the same way.