My Model

Your mental fingerprint.

Every email, Teams chat and channel message gets bucketed into Decide · Respond · Delegate · Analyze · Create · Coach, then projected onto your six mental models. Every brief, draft and reply HumanTronik writes mirrors this.

Action buckets

What you actually do all day.

0%

Decide

Calls a judgment. Closes a loop.

0%

Respond

Acknowledges. Answers. Keeps the thread alive.

0%

Delegate

Hands off. Names an owner. Sets a deadline.

0%

Analyze

Asks for data. Investigates. Quantifies.

0%

Create

Drafts. Proposes. Brings a new shape.

0%

Coach

Feedback. Mentorship. Encouragement.

Leader Profile

The six modes you lead in — and how.

Each bucket below shows the lens, the writing style HumanTronik mirrors, and the tells we've picked up from your own messages.

Decide

0%

Calls a judgment. Closes a loop.

Writing style

Short, declarative sentences. Verdict first, rationale second. Minimal hedging — when you've decided, you commit on the page.

Tells

  • Leads with the verb: 'Approve.' 'Hold.' 'Ship it.'
  • Single-line paragraphs for the call
  • Rationale in 1–2 bullets, never a wall of text

Train your model to surface real examples from your sent items and Teams messages.

Respond

0%

Acknowledges. Answers. Keeps the thread alive.

Writing style

Warm but compact. Mirrors the sender's energy, answers the actual question, and leaves an obvious next step.

Tells

  • Opens by naming the person
  • Restates the ask in one line before answering
  • Ends with a question or a clear handoff

Train your model to surface real examples from your sent items and Teams messages.

Delegate

0%

Hands off. Names an owner. Sets a deadline.

Writing style

Specific owner, specific outcome, specific date. You don't say 'someone should' — you say who, what, by when.

Tells

  • @-mentions or names owners explicitly
  • Always pairs the ask with a deadline
  • Trusts the recipient — no micromanaging follow-ups in the same note

Train your model to surface real examples from your sent items and Teams messages.

Analyze

0%

Asks for data. Investigates. Quantifies.

Writing style

Question-led. You probe assumptions, ask for numbers, and rarely accept a claim without a source.

Tells

  • Phrases like 'what's the actual number on…'
  • Lists the unknowns before proposing a conclusion
  • Pushes back politely when the data doesn't support the narrative

Train your model to surface real examples from your sent items and Teams messages.

Create

0%

Drafts. Proposes. Brings a new shape.

Writing style

Generative and slightly informal. You frame v1s as 'a starting point', invite editing, and prioritize momentum over polish.

Tells

  • Marks drafts as 'rough cut' or 'v0.1'
  • Pairs the idea with the why behind it
  • Invites pushback explicitly: 'tear it apart'

Train your model to surface real examples from your sent items and Teams messages.

Coach

0%

Feedback. Mentorship. Encouragement.

Writing style

Warm, specific, forward-looking. Names what worked first, then the gap, then the next move — never abstract.

Tells

  • Concrete examples instead of generic praise
  • Frames gaps as 'next time, try…' not 'you didn't…'
  • Ends on belief: 'you've got this'

Train your model to surface real examples from your sent items and Teams messages.

Mental models

How you actually think.

Empathy0

How warmly you write

Risk0

How carefully you hedge

Creativity0

How often you reframe

Decision0

How firmly you call it

Speed0

How fast you ship a reply

Reliability0

How often you follow through

Writing voice

How you actually sound.

Train your model to extract your recurring phrasings, hedge words, decisiveness, and signature lines from your sent items.

How HumanTronik uses this

Every reply, brief, and decision — yours.

  • Briefs lead with the bucket you weigh heaviest (Decide vs Coach vs Analyze).
  • Draft replies mirror your hedge level, length, and signature phrasings.
  • Calendar reasoning respects your Risk × Speed posture before suggesting moves.
  • No model weights are changed — your fingerprint is injected into every prompt as context.