Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Problem solving
Test each possible cause of a problem instead of guessing
What you'll learn
Problem vs symptom
Clean problem splits
Root cause
Deciding under uncertainty
Practice
Separate the Problem from the Symptom10 min
Chapter 2
Project scoping
Write a one-page summary of what the work covers
What you'll learn
Central question
Scope boundary
Stakeholder signoff
Issue tree
Practice
Write a 1-page requirements summary25 min
Draft a 1-page project charter25 min
Chapter 4
Process mapping
Map a real process, then check it with the team
What you'll learn
Steps, decisions, owners
Real process path
Process bottleneck
Practice
Mystery-shop a service in 30 minutes30 min
Build a SIPOC for one process20 min
Sketch a simple system architecture30 min
Chapter 4
Spreadsheet models
Build a spreadsheet model whose results update when inputs change
What you'll learn
Model structure
Formula links
Lookup formulas
Sensitivity table
Practice
Analyze Service Times and Propose a Fix30 min
Build a Cost-Benefit Comparison for Two Options25 min
Chapter 5
Communication
Rewrite an update for two different readers, cutting extra lines
What you'll learn
Lead with the point
Match detail to the reader
Said versus heard
Specific feedback
Practice
Write a Six-Line Delay Message10 min
3 more in the plan
Working with othersContribute to group work, ask for help and credit teammatesCh 5
What you'll learn
Early team friction
Clear ownership
Challenge ideas, not people
Lead or follow
Practice
Write a Request That Makes It Easy to Say Yes10 min
Adapting to changeTry a new tool and describe how you handled changeCh 8
What you'll learn
Change vs your response
The messy in-between
Not there yet
Real change vs a feeling
Practice
Map a Change You've Already Survived15 min
Learning new thingsPick what to practise first, then ask one specific questionCh 8
What you'll learn
What you need first
Ask a person
Watching is not knowing
Somewhere safe
Prove it to yourself
Your plan
Chapter by chapter.
12 chapters, in this order. Chapter 1 is free.
1~2 wks
See the work of a Technology Consultant
StartFree
2~2 wks
Scope the problem before you solve it
Skills
31–2 wks
Score help-desk tools for a nonprofit
Project
4~2 wks
Map processes and model the options
Skills
5~2 wks
Make yourself understood across a team
Skills
6~2 wks
Write a technology selection memo
Project
71–2 wks
Talk to two working technology consultants
People
8~2 wks
Learn fast when things change
Skills
9~2 wks
Write a change plan for a rollout
Project
101–2 wks
Answer the questions interviewers ask
Interview
111–2 wks
Decide how you will get in
Decide
12on your timeline
Send your first applications
Apply
The job
What a Technology Consultant does
Helps organizations plan and deliver technology changes by understanding needs, choosing solutions, and guiding implementation so work runs better.
The work
Analyze current processes and systems to find pain points and risks
Gather requirements from users and leaders and turn them into clear specs
Compare solution options and recommend a practical approach and roadmap
Coordinate teams to configure, integrate, and test new tools and systems
Manage project plans, timelines, and budgets and report progress to stakeholders
Train users, write simple guides, and support go-live and early adoption
Monitor results after launch and suggest fixes and next improvements
A typical day
Start with a client check-in to confirm priorities, blockers, and next steps
Run workshops to map processes and capture requirements from users
Work with technical teams on designs, data mapping, and integration questions
Review test results, log issues, and agree on fixes and release timing
End by updating plans and sending a short status note to stakeholders
Tools
Spreadsheets: Excel, Google SheetsPresentations: PowerPoint, Google SlidesProject tracking: Jira, Azure DevOpsDocumentation: Confluence, NotionDiagrams: Visio, LucidchartDatabases: SQLWorkshops: user interviews, process mapping
Ways in
There is more than one route.
Ways to study
Bachelors degree in information systems, computer science, engineering, or business
Diploma or certificate in IT, business analysis, or project management
Bootcamp or short course in data, cloud, or software delivery plus a portfolio
Graduate degree in information systems or business with technology focus
How people get their first job
Apply for consulting internships focused on technology or digital projects
Start in IT support, business analyst, or project coordinator roles
Build a portfolio with process maps, requirements docs, and a simple roadmap
Earn a starter certification like ITIL Foundation, Scrum, or cloud fundamentals
Volunteer to help a club or nonprofit set up tools and document processes
How long does it take to become a technology consultant with Welica?
The plan is 12 chapters, 4–5 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree?
Not always. Common routes are bachelors degree in information systems, computer science, engineering, or business, diploma or certificate in IT, business analysis, or project management, bootcamp or short course in data, cloud, or software delivery plus a portfolio, or graduate degree in information systems or business with technology focus.
What is free?
Chapter 1, See the work of a Technology Consultant, is free for good. Premium unlocks the rest of the plan.