RES 710 Week 2 Descriptive Statistics Example

Reviewed by Davina Cresswell, MBA · University of Phoenix · Updated

This RES 710 Week 2 example describes a real-world style data set with statistics chosen for each variable's level and shape, showing why the median sometimes tells a truer story than the mean. University of Phoenix RES 710 covers descriptive statistics in Week 2, and RES/710 expects DBA learners to summarize central tendency, variability and distribution shape, display data honestly and explain what the numbers mean for the research problem. The data come from the composite Michigan credit union in Week 1, where 1,240 members answered a survey after a transaction and their wait times were drawn from queue records. The paper summarizes each variable, examines skew and outliers in wait time, compares channels and branches, checks the satisfaction scale's reliability and explains what the descriptive picture implies for later inferential tests.

CourseRES 710 Statistical Research Methods and Design I (RES/710)
Week2
Paper typeDoctoral descriptive statistics analysis
Lengthabout 1,161 words, 4 double-spaced pages plus title page and references
FormatAPA 7 student paper
SchoolUniversity of Phoenix
ProgramDBA
UpdatedOctober 2026

Free sample paper for RES 710 Week 2

1

Describing Waits and Satisfaction: Descriptive Statistics for a Credit Union Member Survey

[Student Name]

University of Phoenix

RES/710: Statistical Research Methods and Design I

Week 2 Assignment

[Instructor Name]

[Date]

The learner, the credit union, its members and all data are composites written for a model paper.

What this part is doingThe title names the two key variables the paper describes.
2

Week 1 defined the variables for a composite operations director's study at a Grand Rapids, Michigan, credit union with 24 branches: wait time, service channel, satisfaction, net promoter likelihood and controls such as tenure, age and branch size. Over six weeks, 4,100 members were invited to a short survey within 48 hours of a transaction, and 1,240 responded, a response rate of about 30 percent. Each response was linked to the queue system's wait time for that transaction. This paper describes the data.

Why Describe Before Testing

Field (2018) advises researchers to explore data before any inferential analysis: to examine distributions, spot errors and outliers and check whether data meet the assumptions of planned tests. Descriptive statistics also communicate the basic facts of a study to readers, such as how long members typically wait, which a test statistic alone cannot do.

Service Channel and Member Characteristics

Channel is nominal, so it is described with counts and percentages: 645 branch transactions, 52 percent; 347 phone, 28 percent; and 248 app, 20 percent. Respondents' median age was 46, with app users younger, a median of 34. Median tenure was 11 years. Compared with all members invited, respondents were slightly older and longer-tenured, a pattern to keep in mind when generalizing.

Wait Time

Wait time is ratio-level and applies to branch and phone transactions only, since app transactions have no wait; 992 responses have a wait time. The mean wait was 7.9 minutes, but the median was 5.2 minutes, and the distribution is strongly right-skewed, with a skewness of 2.4. Most members waited under 10 minutes, but a tail of waits stretched beyond 40 minutes, almost all at lunchtime on Fridays at four high-volume branches. The interquartile range was 2.6 to 9.8 minutes.

Micceri (1989) examined 440 real data sets in psychology and education and found that very few were normally distributed; most showed skew, heavy tails or other departures, so assumptions of normality should be checked rather than assumed. The credit union's wait times are a clear case.

What this part is doingLinking the skew to Micceri's findings shows that non-normal data are the norm, not a flaw.
3

Screening the File

Before computing summaries, the learner checked every variable's minimum and maximum against its possible range. Two ages of 112 and one tenure of 64 years were traced to typing errors in member records and corrected from the source system. Duplicate responses from the same member within one week were reduced to the first one.

Spread Beyond the Standard Deviation

For wait time, the standard deviation of 7.1 minutes is almost as large as the mean, which signals heavy skew rather than wide spread in the usual sense. Reporting it alone would suggest that negative waits are plausible, which is impossible. The interquartile range of 7.2 minutes, the 90th percentile of 16.5 minutes and the maximum of 58 minutes together give readers a clearer sense of what a typical member experiences and how bad the worst waits become. For management, the 90th percentile may matter most, since it shows how long one member in ten waits.

Actual Versus Perceived Wait

Week 1 also added a survey question on each member's sense of how long the wait lasted. Perceived waits had a median of 7 minutes, almost two minutes longer than the recorded median, and members who waited more than 10 minutes overestimated by a wider margin. The correlation between recorded and perceived wait, computed with Spearman's rho because both are skewed, was .58, a moderate association. This gap suggests that perception adds information beyond the clock, which later regression models can test.

What this part is doingUsing a rank-based correlation for two skewed variables matches the statistic to the data.
4

Missing Data

Of the 1,240 responses, 31 left one or more satisfaction items blank and 18 skipped the net promoter item. Scale scores were computed when at least three of four items were answered, which kept all but nine cases. No wait times were missing for branch or phone transactions, since they came from system records. Missing responses were slightly more common among members over 70, a pattern to report but too small to change the descriptive results.

Outliers

Twelve waits exceeded 40 minutes. Checking queue logs showed they were real, not errors: members who took a ticket and then waited through a system outage on two Fridays. They are not deleted, since they reflect actual member experience, but analyses will be run with and without them to see whether they change conclusions.

Satisfaction

Satisfaction is the mean of four items rated 1 to 7. Across all 1,240 respondents, the mean was 5.4 (SD 1.2) and the median 5.5. The distribution is mildly left-skewed, with most members satisfied and a smaller group very dissatisfied. Internal consistency was high, with Cronbach's alpha of .89, supporting the use of the average as a single score.

By channel, mean satisfaction was 5.3 for branch, 5.2 for phone and 6.0 for app users. These are descriptive differences that Week 5's t tests and later analyses will test.

Net Promoter Likelihood

The 0-to-10 item had a median of 8, with 41 percent scoring 9 or 10, 37 percent scoring 7 or 8 and 22 percent scoring 6 or lower. Because the item is ordinal, the median and the category percentages describe it better than the mean.

Members who used the app scored about three-quarters of a point higher on satisfaction, but they also never stood in a line.

Branch Differences

Branch medians for wait time ranged from 2.1 to 11.4 minutes. A box plot by branch shows that the four branches with the longest waits also have the widest spread and the lowest median satisfaction. This pattern suggests that branch-level factors, such as staffing, may matter and that later analyses should account for members being clustered in branches.

Displaying the Data

Weissgerber et al. (2015) reviewed published figures and found that bar graphs of means were widely used for continuous data even though they hide the distribution, sample size and outliers, and they recommended showing individual data points, box plots or histograms instead. The learner's report will use a histogram for wait time, box plots of wait time and satisfaction by branch and a dot plot of satisfaction by channel, rather than bar charts of means.

What this part is doingChoosing displays that reveal distributions follows current guidance on honest data presentation.
5

Implications for Later Analyses

Wait time's skew suggests a log transformation or rank-based tests when it is a variable in comparisons; regression with wait time as a predictor is less affected, but residuals must be checked. Satisfaction is close enough to normal, given the sample size, for t tests and regression. Clustering by branch should be addressed in later models. App users differ from others in age as well as channel, so comparisons should control for age.

Conclusion

The descriptive picture is clear: most members wait about five minutes, a few wait much longer at busy times, satisfaction is generally high but lower for branch and phone users and branches differ substantially. Choosing medians for skewed waits, frequencies for categories and distribution-revealing graphs gives an honest summary and sets up the inferential tests of Weeks 4 through 6.

6

References

Field, A. (2018). Discovering statistics using IBM SPSS statistics (5th ed.). Sage.

Micceri, T. (1989). The unicorn, the normal curve, and other improbable creatures. Psychological Bulletin, 105(1), 156-166. https://doi.org/10.1037/0033-2909.105.1.156

Weissgerber, T. L., Milic, N. M., Winham, S. J., & Garovic, V. D. (2015). Beyond bar and line graphs: Time for a new data presentation paradigm. PLoS Biology, 13(4), e1002128. https://doi.org/10.1371/journal.pbio.1002128

What the RES 710 Week 2 instructions ask

The second RES 710 paper asks doctoral learners to compute and interpret descriptive statistics. Prompts may ask for measures of central tendency, variability and shape for each variable, frequency tables for categorical variables, appropriate graphs such as histograms and box plots, identification of outliers and a written interpretation linking the statistics to the research question, often using SPSS or Excel output. Some versions ask learners to check assumptions for later tests. Use a real or realistic data set from the learner's research interest, choose statistics suited to each variable's level and distribution and cite statistics texts and research in APA. Explain what the descriptive results suggest about the inferential analyses to come.

How this RES 710 Week 2 example is built

Our model paper summarizes 1,240 survey responses. Wait time is strongly right-skewed: the mean is 7.9 minutes, the median 5.2 and a few lunchtime waits exceed 40 minutes, so the median and interquartile range describe it better. Satisfaction, a four-item scale averaged from 1 to 7, has a mean of 5.4, a standard deviation of 1.2 and good internal consistency. Channel shows 52 percent branch, 28 percent phone and 20 percent app transactions. Research on non-normal distributions in real data cautions against assuming normality, and research on data display argues for showing distributions rather than bar charts of means. Comparisons by channel and branch reveal patterns worth testing, and the paper notes which later tests will need transformations or rank-based alternatives.

RES 710 Week 2 grading rubric: where the points go

Doctoral graders reward descriptive analysis that fits the data rather than reporting every statistic. Strong papers choose measures suited to each variable's level and shape, report them accurately with units and sample sizes and use graphs that show distributions honestly. Credit goes to identifying skew and outliers and explaining how they will be handled, to checking scale reliability and to interpreting descriptives in terms of the research problem. Graders also value a clear link between the descriptive picture and assumptions for later tests, and a short note on missing data and how it was treated. Exact figures for every statistic, with sources cited in APA, finish the work.

RES 710 Week 2 help: mistakes to avoid

Many descriptive analyses report means and standard deviations for every variable, including categories and skewed data. Choose statistics by level and shape: frequencies for categories, medians and interquartile ranges for skewed variables. Another frequent gap is ignoring outliers or deleting them without reason; investigate them first. Learners also present bar charts of means that hide distributions; use histograms or box plots. Some papers list numbers without interpretation; say what each result means for the research problem. Finally, note which later tests the descriptive results affect, such as whether normality is reasonable. Tutors can help you pick a display that suits each variable.

Related RES 710 sample papers

Other RES 710 week samples

More DBA sample papers

RES 710 Week 2 questions, answered

What does RES 710 Week 2 usually cover?

It usually covers descriptive statistics: central tendency, variability and distribution shape, frequency tables, graphs, outliers and interpretation linked to a research question.

Where can I find a free RES 710 Week 2 sample paper?

The RES 710 Week 2 descriptive analysis of a credit union survey is above, open to every reader.

When should you report the median instead of the mean?

When values bunch on one side with a long tail or include extreme cases, as wait times and incomes often do, since the median is not pulled toward extreme values.

What is the interquartile range?

The range covered by the middle 50 percent of values, from the 25th to the 75th percentile, which describes spread without being affected by extremes.

How do you check whether data are normally distributed?

By examining histograms and Q-Q plots, skewness and kurtosis values and formal tests, keeping in mind that large samples make small departures statistically significant.

Write yours, or have the desk draft it

This paper is an original model document written by our desk, not a submitted student paper and not an official University of Phoenix document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.