MGMT 645 Week 8 Integration of Faith and Learning Example

Faithful Work Done Well: A Christian Worldview of Quality Planning, Assurance and Control in Projects

Introduction

Quality management is usually taught as a technical discipline, with its standards, metrics and control charts. Yet every quality decision is also a decision about how one person's work will affect another. When a project team defines a defect, it is deciding whose experience counts; when it checks its process, it is deciding whether to do the work honestly even where no one is watching; and when it reports results, it is deciding whether to tell the truth. This paper argues that a Christian worldview gives each of the three quality processes taught in this course a moral foundation: quality planning expresses the call to serve one's neighbor through work done well, quality assurance expresses integrity in the way work is done, and quality control expresses truthfulness in measuring and reporting results.

Work and Stewardship

The Christian understanding of work begins in Genesis, where the first human is set in Eden with the task of tending and guarding it (English Standard Version Bible, 2001/2016, Genesis 2:15). Work is part of creation's design, given before the fall rather than as a punishment for it. Keller and Alsdorf (2012) argue that ordinary work is a way of serving God and loving one's neighbor, and that its value does not depend on whether it is religious work. Their account means that a project manager's care for quality is not a secular concern separate from faith. It is one of the main ways a Christian in management serves others. Van Duzer (2010) adds that business exists to provide goods and services that help a community flourish and meaningful work through which people can express their gifts. Quality is the measure of whether a project does the first, and the way it is pursued shapes the second.

Quality Planning and Service to the Neighbor

The PMBOK Guide describes quality planning as identifying the quality requirements and standards for a project and documenting how they will be met (Project Management Institute, 2017). The key question in planning is whose requirements matter. Jesus summarized the Law and the Prophets in the command to do to others what one would have them do to you (English Standard Version Bible, 2001/2016, Matthew 7:12). Applied to quality planning, that command asks a team to define quality as the people on the receiving end of its work would define it. In the client portal project from this course, the firm could have defined success as a working system. Instead, it defined its defects from the clients' experience, an incomplete upload that would hold up a return and a document sent to the wrong person, and set targets for both. That choice was technical, but its motive was service.

In Rose (2014), good results come chiefly from preventing defects in advance, with end-of-line inspection a weak substitute. Prevention also has a moral dimension. A team that waits for defects to appear lets someone else bear their cost, whether a customer, a coworker or a patient. Planning quality in from the start is a way of taking responsibility for one's work before it reaches another person.

Quality Assurance and Integrity

Quality assurance concerns the processes by which work is done, checking that they are sound enough to produce good results. Scripture repeatedly connects faithfulness with integrity in process. The law given to Israel forbade cheating in length, weight or quantity and required scales and measures that were true (English Standard Version Bible, 2001/2016, Leviticus 19:35-36), a concern not with any single sale but with the instruments by which all sales were made. Quality assurance is concerned with instruments in the same sense: the checklists, procedures and reviews that determine whether every product will be right, not just the one being inspected.

Deming (1986) held that the bulk of defects are built into the system that managers design, so the duty to improve it rests with management rather than with the people on the line. A Christian reading of that insight adds a pastoral dimension: blaming workers for defects that the system produces is not only poor management but unjust. In the portal project, the pilot's leading defect, missing brokerage statements, came from the firm's own checklist wording, not from careless clients. Fixing the checklist rather than scolding clients was both better quality practice and a fairer way to treat the people the firm served.

Quality Control and Truthfulness

Quality control measures outputs to determine whether they meet requirements. Its moral core is truthfulness. Paul told the Ephesians to stop lying and to tell their neighbors the truth, because they were members of one body (English Standard Version Bible, 2001/2016, Ephesians 4:25). In projects, the temptation to shade results is constant: a percentage complete rounded up, a defect reclassified, a pilot result described as encouraging. When the portal pilot reached only 60 percent complete first uploads against an 85 percent target, the honest response was to report the number and analyze it, which led to the improvements that brought the season's result to 87 percent. Truthful measurement is not only an ethical duty; it is the condition for improvement, because a team cannot fix what it will not admit.

Continuous Improvement and Grace

Quality management assumes that work can always be improved, which raises a spiritual danger: perfectionism, the belief that one's worth depends on flawless results. Paul offers a different posture. He wrote that he had not already obtained the goal or been made perfect, but pressed on toward it, forgetting what lay behind (English Standard Version Bible, 2001/2016, Philippians 3:12-14). Christian project managers can pursue continuous improvement with the same freedom, holding high standards without being crushed by their failures, because their identity rests on grace rather than performance. That posture also makes honest reporting easier, since a defect becomes information to act on rather than a threat to be hidden.

Conclusion

A Christian worldview does not supply new quality tools, but it changes why and how the tools are used. Quality planning becomes a way of serving the neighbor by defining quality from the experience of those the work affects. Quality assurance becomes a matter of integrity in the processes that shape every result. Quality control becomes an exercise in truthfulness about what the work has achieved. Held together by grace, these commitments allow a project manager to pursue excellence as an act of service rather than of self-justification, and to treat every defect found as a chance to serve others better.

References

Deming, W. E. (1986). Out of the crisis. MIT Center for Advanced Engineering Study.

English Standard Version Bible. (2016). Crossway. (Original work published 2001)

Keller, T., & Alsdorf, K. L. (2012). Every good endeavor: Connecting your work to God's work. Dutton.

Project Management Institute. (2017). A guide to the project management body of knowledge (PMBOK guide) (6th ed.).

Rose, K. H. (2014). Project quality management: Why, what and how (2nd ed.). J. Ross Publishing.

Van Duzer, J. (2010). Why business matters to God (and what still needs to be fixed). IVP Academic.