Start Difficult ERPNext Tasks by Looking Away from the Cliff

In Happy Feet, there is a memorable cliff-jump scene involving Ramón. He is afraid to jump, so he tries to trick himself. Instead of looking down at the frightening drop, he turns away, points in another direction, and says, “Boy, look at that!” Then, while trying not to confront the cliff directly, he accidentally falls backward over the edge.

It is a funny animated moment, but it captures something very real about difficult work.

Sometimes the task is not impossible. The problem is that looking directly at the full size of the task makes it feel impossible.

This happens often in ERPNext implementations, reconciliations, reporting, support, and project follow-ups.

A reconciliation task may look massive. A “get things done” task may sound shallow but actually require thought. A client clarification may look simple but hide many decisions. A report may sound easy until one asks what the source of truth is.

The lesson from Ramón is not to be careless. It is that sometimes we need a psychological entry point into difficult work. We need to stop staring at the cliff and create a first step that is small enough, safe enough, or indirect enough to begin.

In business work, this is not avoidance. It is controlled entry.

The cliff is not always the task

When someone delays a task, we often assume the person lacks discipline.

But in many business and ERPNext contexts, the delay usually comes from one of three causes:

1. The task looks too large.
2. The task is unclear.
3. The task appears inefficient unless a better method is used.

These are different problems, and they need different responses.

A person delaying a reconciliation may not be avoiding work. They may be avoiding the feeling that the work will consume an entire day if done manually.

A person delaying a vague follow-up may not be careless. They may not know what “done” actually means.

A person delaying a report may not be slow. They may be waiting for the missing business logic that makes the report meaningful.

So the better question is not:

“Why has this not been done?”

The better question is:

“What is stopping this task from becoming startable?”

Reconciliation tasks feel large because the wrong starting point is visible

A reconciliation task can look frightening because the visible version of the task is usually:

“Compare everything.”

That is the cliff.

If someone imagines comparing hundreds or thousands of transactions line by line, delay is natural. The brain resists because it already knows the method is inefficient.

The better starting point is not comparison.

The better starting point is method design.

Before reconciling, define:

Area	Question
Data sources	What are we comparing? Bank statement, ERPNext ledger, invoices, payment entries, stock ledger, or external system?
Matching keys	Are we matching by date, amount, reference number, party, invoice number, or narration?
Exact matches	Which records can be cleared automatically or semi-automatically?
Probable matches	Which records need fuzzy matching or tolerance rules?
Exception types	What categories explain the differences?
Corrective actions	What should happen after each difference is identified?

This changes the task from:

“Reconcile everything.”

to:

“Design the matching rules, remove exact matches, then investigate exceptions.”

That is far less intimidating.

A better way to start reconciliation

For reconciliation work in ERPNext, the first step should usually be:

“Define the reconciliation technique before touching individual records.”

A practical flow could be:

1. Export the two data sources.
2. Normalize dates, references, parties, and amounts.
3. Match exact reference number and amount.
4. Match date and amount where references are missing.
5. Identify one-to-many and many-to-one cases.
6. Classify unmatched records.
7. Work only on exceptions.
8. Prepare corrective entries or follow-up actions.

The power is in reducing the comparison set.

The task is no longer a mountain of transactions. It becomes a controlled exception-handling process.

Exception categories reduce anxiety

One reason reconciliation feels difficult is that every difference looks unique at first.

But most differences fall into repeatable categories.

Exception category	Meaning
Timing difference	Entry exists in both systems but in different periods
Missing in ERPNext	Transaction exists externally but not in ERPNext
Missing in external source	ERPNext has the entry, but the external source does not
Amount mismatch	Same transaction, different value
Duplicate entry	Same transaction entered more than once
Bank charges	Charges deducted by bank but not booked
Wrong reference	Transaction exists but the reference number is incorrect
Wrong party	Amount exists but is mapped to the wrong customer or supplier

Once these categories are defined, the work becomes manageable.

The goal is not to “find chaos.” The goal is to classify differences into known buckets.

Vague tasks are a different type of cliff

Now consider a different kind of task:

“Get things done.”

This sounds simple, but it is not a task. It is a container.

It may include:

• Follow up with the client
• Review pending issues
• Prepare a status update
• Ask for missing information
• Confirm scope
• Check unresolved errors
• Update the project plan
• Escalate blockers
• Close open support tickets

The task looks shallow, but it requires thinking before action.

That is why people delay it. Not because it is large in volume, but because it is unclear in shape.

Convert vague work into visible next actions

A vague task should not be executed immediately. It should first be translated.

For example:

Vague task	Better next action
Get things done	List pending items from the last meeting
Follow up	Send three clarification questions to the client
Prepare update	Summarize completed, pending, blocked, and next actions
Check issue	Reproduce the issue and capture the error message
Work on reconciliation	Identify data sources and matching rules
Finalize scope	Separate confirmed scope, assumptions, exclusions, and open questions

The question is not:

“Why have I not started?”

The better question is:

“What is the first visible action?”

The backward-step technique

The Ramón cliff scene works as a useful metaphor because it shows a psychological trick:

Do not stare directly at the full drop. Turn the task around and take the smallest safe step.

In work terms, this means avoiding the full emotional weight of the task and starting from the least threatening entry point.

For reconciliation:

Do not start with all unmatched transactions. Start by defining matching keys.

For reporting:

Do not start with the final report. Start by writing the business question the report must answer.

For client follow-up:

Do not start with the full email. Start by listing what you need from the client.

For issue resolution:

Do not start with fixing the issue. Start by reproducing it.

For project management:

Do not start with “clear all pending items.” Start by classifying them into completed, pending, blocked, and unclear.

This is not avoidance. It is controlled entry.

Two types of difficult tasks

Most delayed tasks fall into two categories.

Task type	Why it gets delayed	Correct response
Large but solvable	It feels too time-consuming without a method	Design the method first
Shallow but unclear	It sounds simple but lacks definition	Clarify and elaborate first

Reconciliation is usually the first type.

“Get things done” is usually the second type.

Both require a first step, but not the same first step.

How ERPNext teams can apply this

In ERPNext projects, many tasks combine business process, data, configuration, reporting, and user behavior. This makes vague assignment dangerous.

Instead of assigning:

“Do bank reconciliation.”

Assign:

“Compare the April bank statement with ERPNext payment entries. Match first by reference number and amount. Then classify unmatched records as timing difference, missing in ERPNext, missing in bank, bank charge, duplicate, or amount mismatch.”

Instead of assigning:

“Get pending items done.”

Assign:

“Create a pending-action list from the last meeting with owner, status, blocker, and next action.”

Instead of assigning:

“Check the issue.”

Assign:

“Reproduce the issue, identify the DocType, capture the error message, confirm the user role, and document whether it happens during save, submit, cancel, or print.”

The clearer the entry point, the faster the task starts.

How managers can assign better tasks

Managers and project leads can reduce delay by changing how work is assigned.

A good task assignment should include:

Element	Why it matters
Expected output	Makes “done” clear
Data source	Prevents confusion about where to begin
Method	Reduces inefficient execution
Owner	Creates accountability
Deadline	Sets priority
Exception handling	Prevents unnecessary escalation
Next action	Makes the task startable

For example, a weak task assignment is:

“Reconcile supplier balances.”

A better task assignment is:

“Reconcile supplier balances for March 2026 using the supplier ledger, purchase invoices, payment entries, and supplier statement. Match by invoice number and amount first. Then classify differences as missing invoice, missing payment, timing difference, debit note, credit note, or amount mismatch.”

This gives the user a path, not just a responsibility.

How consultants can unblock themselves

When you notice yourself delaying a task, do not immediately blame discipline.

Ask:

“Is this task undefined, inefficient, or emotionally heavy?”

Then use the right response.

Blocker	Better response
Undefined	Clarify the expected output
Inefficient	Design the method first
Too large	Break it into stages
Knowledge gap	List questions or research points
Fear of starting	Reduce the first action
Time dread	Timebox only the first step

For ERPNext consultants, this habit is especially useful because implementation tasks often combine business process, system configuration, reporting, data validation, user training, and client communication.

A task that looks simple may hide many decisions.

A simple starting framework

Before beginning a task that feels delayed, ask three questions.

1. Is this task large because of volume?

If yes, create a technique first.

Example:

“I will define the matching rules before reconciling.”

2. Is this task difficult because it is vague?

If yes, clarify the expected output.

Example:

“I will convert this into three specific next actions.”

3. Is this task emotionally heavy because the first step feels too big?

If yes, reduce the first step.

Example:

“I will only create the document title and headings.”

This is how one avoids staring at the cliff.

The first step should feel almost too small

The first action should not be heroic.

It should be small enough that the mind does not resist it.

Examples:

Difficult task	Small first step
Reconcile bank statement	List the matching keys
Prepare project update	Create four headings: completed, pending, blocked, next
Build report	Write the business question
Fix issue	Reproduce the error once
Follow up with client	List the missing clarifications
Review migration data	Pick one account or item group for sample validation
Prepare proposal	Copy the previous proposal structure

This is the business equivalent of not looking down.

You are not denying the size of the task. You are creating a safe entry point.

Final recommendation

Some tasks should not be started directly.

They should be approached indirectly.

For reconciliation, do not begin with manual comparison. Begin with matching rules, exception categories, and a method that reduces the workload.

For vague tasks, do not begin with execution. Begin by defining what “done” means.

For intimidating work, do not stare at the full task. Turn around, take the smallest safe step, and let momentum do the next part.

The lesson is simple:

When the task looks impossible, do not keep looking down. Create a first step that your mind can accept.

That is often enough to begin.

Reference articles and discussions

• No external reference articles or discussions were used.
• This article was developed from an internal discussion on task resistance, reconciliation work, vague task definitions, and practical execution methods in ERPNext and business operations contexts.
• The opening analogy references the Ramón cliff-jump scene from Happy Feet, as recalled and corrected during the discussion.

---

Aakvatech Limited is a Frappe Gold Partner and ERPNext implementation company headquartered in Dar es Salaam, Tanzania, operating across East Africa and the UAE.

This article was co-created using AI to accelerate drafting, with final insights curated and validated by the author. Any customer, personal, or sensitive data referenced during drafting has been anonymized or masked where applicable. All contributors, reference URLs, tools, and materials used to assist this content curation are credited in the Reference section.