Problem Solving — Explained
Detailed Explanation
Define the decision before solving it
Problem solving is the process of moving from an unsatisfactory situation to a defensible action using evidence, constraints and a clear objective. In CSAT, the question may involve numerical reasoning, interpreting information or selecting a course of action.
The first task is to identify what counts as success. Reducing average waiting time, serving the most urgent cases and keeping expenditure within a fixed budget are related but different objectives. A solution can perform well on one while failing another that the question treats as essential.
Separate the problem, cause and proposed remedy
Consider an original hypothetical service-centre example. Applicants wait a long time before receiving documents. That is the observed problem. A staff shortage is one possible cause, while hiring staff is one possible remedy.
Neither follows automatically from the waiting-time observation. Delays may instead arise from incomplete forms, repeated verification, uneven arrival times or a software outage. Calling the problem a need for more staff already commits to a causal explanation that has not been tested.
A useful problem statement specifies who is affected, what is happening, when it happens and what evidence establishes the gap. For example, during the observed morning period, a queue is growing because arrivals exceed completed services. This statement is narrower and more testable than saying that the entire department is inefficient. It also leaves room for several interventions. The wording should be precise enough to guide action without assuming the conclusion.
Use quantities to test feasibility
Suppose applicants arrive at a steady average of 24 per hour during a three-hour period, and one counter completes 18 services per hour. Ignoring an initial queue and random variation, the backlog grows by six per hour, reaching 18 after three hours.
A second identical counter would raise nominal capacity to 36 per hour, exceeding arrivals. But this arithmetic alone does not establish that a second counter is the best solution. Its staffing cost, availability and ability to handle the same tasks remain relevant constraints.
If incomplete forms cause a third of applicants to repeat a verification step, a preliminary help desk may reduce the workload without duplicating the final service counter. That possibility requires evidence about how much time the repeated work consumes.
Do not infer a precise capacity gain merely from the share of incomplete applications. Counts, durations and process dependencies are different measurements. A strong solution identifies the additional information that could change the decision.
Distinguish constraints from preferences
A constraint is a condition an admissible solution must satisfy, such as a stated budget ceiling, a legal requirement or a minimum safety standard. A preference helps compare solutions that meet the constraints, such as convenience, speed or lower administrative burden. If the question requires a response within two days, an otherwise attractive month-long reform does not solve the immediate task. It may belong in a separate long-term plan, but it cannot replace the required short-term action.
Conversely, a familiar practice is not automatically a binding constraint. If the scenario says staff have traditionally processed files in one order, ask whether the order is legally required, technically necessary or simply customary. Treating every existing practice as fixed can hide feasible improvements. Treating an explicit rule as optional can produce an efficient-looking but inadmissible answer. Read the source of each limitation carefully.
Generate and compare genuine alternatives
In the service-centre example, alternatives might include adjusting staff rosters to arrival peaks, improving form instructions, separating simple renewals from complex cases, or adding capacity. Compare them using the same criteria: expected reduction in delay, cost, accessibility, implementation time and risk of excluding vulnerable applicants.
A comparison is unfair if one option is judged by its best possible outcome while another is judged by its worst. State the assumptions supporting each estimate.
Some options can be combined. Clear instructions may complement a revised roster rather than compete with it. Other combinations may be infeasible because they rely on the same limited staff. Check resource dependencies before adding their estimated benefits. Two interventions that remove the same repeated verification step do not necessarily produce twice the saving. The same overlap problem appears in numerical counting and in administrative planning.
Test causes before scaling a remedy
A small pilot can provide evidence when uncertainty is material and the intervention is reversible. For instance, compare similar time periods before and after a form-help desk is introduced, while recording arrival volume and staffing.
A fall in waiting time is encouraging, but changes in demand or case complexity may also explain it. The comparison should distinguish the intervention's likely effect from coincidental variation. A pilot is not a substitute for an urgent protective action when the scenario presents immediate serious harm.
Define the evaluation measure before seeing the result. Average waiting time can improve while the longest waits become worse, so distributional measures may matter. Counting completed applications without checking errors could reward speed at the expense of correctness. Select measures that reflect the actual objective and relevant safeguards, rather than the easiest number to report.
Explain the selected action and its limits
A defensible answer connects evidence to an action, acknowledges the key trade-off and identifies how success will be checked. In an objective question, the best option is often the one that addresses the stated problem within the given constraints while preserving necessary safeguards. It need not be the most ambitious reform imaginable. Do not import facts that the question does not provide or choose a dramatic response simply because it sounds decisive.
These examples are original practice in analytical and decision reasoning. The UPSC syllabus supplies broad alignment, not a guarantee that a particular administrative scenario will appear. Written exercises below are a way to make the reasoning explicit; CSAT itself is an objective Preliminary Paper II examination.