Daniel Praneeth

WORK SAMPLES / OCTOBER 2026

Inspect the design.
Work through the decision.

Four newly authored practice samples with fictional scenarios. They demonstrate current learning and workflow design, separately from historical employer deliverables and measured business results.

Download work samples

INDEPENDENT PRACTICE SAMPLE / Decision practice & job aid

CRM qualification: evidence before progression

Learning goal. Distinguish a positive buying signal from sufficient evidence for the next commercial decision.

Fictional scenario: an operations lead at Northstar Works attends a product demonstration and says the solution looks useful. A seller estimates possible savings, but the buyer has not validated a baseline. The decision authority and procurement path are unknown.

Learner decision

The seller wants to advance the opportunity. What should the record and next conversation contain?

CheckWorked response
Buyer commentRecord interest as a signal, with its source and date.
Value estimateLabel the estimate as a hypothesis until the buyer validates the problem, baseline and desired outcome.
Buying processIdentify decision authority, criteria and procurement steps; record unknowns explicitly.
Next actionAgree who will clarify the missing evidence, what they will bring and when.

Worked response

Capture the customer signal, distinguish it from assumptions, and plan the missing qualification work. Follow the organisation’s approved progression criteria rather than inventing an exit rule.

Design rationale

Teach the decision before the screen sequence. A learner must explain what evidence is missing, not only remember where to click.

How to assess it

Four observable checks: identifies the source; separates fact from estimate; names missing buying-process evidence; specifies an owner and next action.

INDEPENDENT PRACTICE SAMPLE / Readiness checklist & worked decision

Release readiness: a decision-led checklist

Learning goal. Connect changed tasks, learning readiness and unresolved operational risks before a release.

Fictional scenario: Atlas Service is changing approval routing for coordinators, managers and support teams. Guidance has been reviewed, but coordinator permissions have not yet been tested.

Learner decision

Is the release communication ready to announce that everyone can use the new workflow?

CheckWorked response
Changed tasksVerified: each role has a task-level change summary and support route.
Process reviewVerified: process owner has reviewed the guidance.
Role accessOpen: coordinator permissions still need a successful task test.
Learning supportPrepared: quick guide, practice task and support contact are available.
Launch decisionPending: business release owner must resolve or formally accept the access risk.

Worked response

Prepare the communication, but do not state that access is ready. Name the open permission test, its owner and the decision needed. The business release owner decides whether to launch, delay or accept a documented exception.

Design rationale

Make unresolved task execution a visible readiness issue. Content completion alone is insufficient to declare users ready.

How to assess it

The checklist connects each open issue to a role, evidence requirement, owner and release decision.

INDEPENDENT PRACTICE SAMPLE / Reporting workflow & measurement example

Learning operations: completion is not competence

Learning goal. Produce a cohort-specific completion report and interpret its limits correctly.

Fictional dataset: twelve unique learners are assigned to Practice A. Ten are marked complete and two incomplete at one defined snapshot. There are no withdrawn or duplicate assignments.

Learner decision

What can you report, and what additional evidence would establish readiness?

CheckWorked response
Define the cohortUse Practice A only, with a stated reporting date and assignment definition.
Verify the recordsCheck twelve unique assignments, ten complete and two incomplete; reconcile the export against the filtered preview.
Calculate completion10 ÷ 12 × 100 = 83.3%, rounded to one decimal place.
Report scopeDescribe assignment completion at the snapshot, not task competence or productivity.
Check applicationUse a task demonstration, manager observation or assessed practice to investigate readiness.

Worked response

Report 83.3% completion for this fictional cohort and snapshot. Follow up with the two incomplete learners. Keep applied task performance separate from completion and do not infer ramp time from this calculation.

Design rationale

Define the denominator and verification step before presenting a percentage.

How to assess it

The worked result is reproducible from the stated fictional counts. It is a teaching calculation, not an AVEVA metric.

INDEPENDENT PRACTICE SAMPLE / Production checklist & worked revision

Learning-media QA: a visible before-and-after

Learning goal. Check meaning, terminology, caption alignment and readability before publishing learning media.

Original fictional example: a clip says “Review the Northstar account before saving,” while its caption says “Review the North Start account before saving.” The next instruction appears on screen while the previous caption is still visible.

Learner decision

What must change, and what would confirm that the correction holds?

CheckWorked response
TerminologyCorrect “North Start” to “Northstar” and check it against the fictional narration.
TimingAlign the instruction change with the relevant narration and caption interval.
ConsistencyUse a consistent visual treatment for the same record type across the clip.
VerificationReplay the corrected interval, then review the exported subtitle file and the next transition.

Worked response

Correct the term, align the transition and replay the output. A logged correction is a revision; a replay or output check establishes whether it is resolved.

Design rationale

Treat subtitles and on-screen guidance as one learner experience rather than separate files to approve.

How to assess it

Before/after differences and the verification action are explicit. This example demonstrates a QA method, not measured error reduction.

Back to career work