Whom to interview, which records to request, what to watch at the counter and how to tell symptoms from causes: a storage client's IT402 Unit 4 discovery plan covers each. Searches like "it 402 unit 4 assignment example", "it402 unit 4 sample" and "it402 unit 4 example" land here.
What a finished IT402 Unit 4 client discovery plan looks like
A purpose statement opens the five pages, naming the decision discovery must support: whether the client's problem is its website, its operations or both. A stakeholder map lists eleven people to interview, including the owner, his daughter as operations director, the bookkeeper, and three facility managers chosen deliberately: the busiest site, a rural site on DSL, and the newest. An interview guide gives each group six to eight open questions and two follow-ups, such as walk me through the last reservation that came in online. A records request asks for three months of web reservations, rent rolls, gate access logs and the monthly occupancy spreadsheet. An observation plan times one move-in from inquiry to gate code. A symptom-and-cause worksheet, a two-stage schedule, and a confidentiality note close the plan.
How a IT402 Unit 4 example is structured
The plan works backward from the decision discovery has to inform, so every interview question and records request traces to one of three competing explanations: the website loses customers, the handoff from web to facility loses them, or rates and availability are wrong when customers arrive. Holding the owner's explanation as one hypothesis among three keeps the plan from confirming what the client already believes. Interviews are sequenced from the owner outward, then back to him, so his view is heard first and tested last. Records are requested before the facility visits, because numbers make interview answers checkable. Observation is included because what staff say they do and what the counter shows often differ. Questions are open and anchored in recent events rather than opinions. The worksheet sorts each finding as symptom or cause.
Three explanations to test
The website, the web-to-facility handoff, or stale rates and availability, each tied to the questions and records able to support or eliminate it.
Eleven people, chosen on purpose
The owner, his daughter, the bookkeeper, three contrasting facility managers, the part-time support person, two relief staff and two customers who reserved online.
Questions about last Tuesday
Interview items ask for recent specific events, such as the last reservation received, because accounts of what usually happens drift toward how things should work.
Records before visits
Web reservations, rent rolls, gate logs and the occupancy spreadsheet are requested first, so claims heard at the facilities can be checked against numbers.
One move-in, timed
An observer follows a customer from first inquiry to working gate code and notes every re-keyed field and phone call along the way.
Symptom or cause
A worksheet sorts findings as they arrive, so a complaint about the website is logged as a symptom until the records show where reservations are lost.
Where marks go in IT402 Unit 4
Discovery plans lose points most often by planning to confirm the client's diagnosis instead of testing it. A list of interview questions aimed at what the new website should include has already chosen the solution. Stakeholder lists that stop at the person who signs the contract miss the staff who see the problem daily. Closed or leading questions, such as whether reservations are handled promptly, invite the answer the client wants to give. Plans that rely on interviews alone, with no records or observation, leave nothing to check claims against. An explicit distinction between symptoms and causes is expected in many sections, as are listening techniques stated as practices rather than virtues. Missing schedules, no confidentiality statement, and no link between each question and the decision it serves complete the list of usual deductions.
Get a IT402 Unit 4 example written to your instructions
Discovery prompts in IT402 tend to supply a short case and ask for the plan that would come before any proposal. Built from that case, the Unit 4 instructions and the rubric, plus any interview template in use, the plan names your client's own people and records. Allow 24-48h; a first custom sample is free.
IT402 Unit 4 questions, answered
What is the difference between a symptom and a cause in discovery?
A symptom is what the client notices: customers complain the website is hard to use, occupancy is flat. A cause is what produces it, often somewhere the client is not looking, such as online reservations emailed to a facility that nobody checks on weekends. Discovery treats every early complaint as a symptom until evidence locates the cause, and the sample's worksheet makes that sorting visible.
How many interview questions should a discovery plan include?
Enough to cover each hypothesis without turning an interview into a survey. Six to eight open questions per stakeholder group, with a few prepared follow-ups, fit a 45-minute conversation. Rubrics usually care more about question quality than count: open wording, recent specific events, and a clear link to what the engagement must decide. Your section may set a number, and the sample follows it.
Should customers be interviewed, or only the client's staff?
Where the case allows it, a few customers add evidence staff cannot supply, especially about what happens before anyone at the business hears from them. The sample includes two customers who reserved online, recruited through the client with their consent. If your scenario limits contact to the client organization, that line is removed and the records request carries more of the weight.