Philosophy-Driven Framework Reshapes Precollege Engineering
Engineering entered public school curricula in the late 20th century through technology education, gaining explicit presence in K–12 discourse in the early 2000s. Alongside this rise, design-based learning emerged as a counterpart to inquiry-based science, and integrated STEM approaches began using design challenges to teach interconnected concepts. While research has demonstrated design’s pedagogical benefits in science, engineering, mathematics, and even literacy, fewer studies have provided clear epistemological justification for precollege engineering. Addressing this gap, the honeycomb of engineering framework builds on philosophical foundations to guide educational practice.
Philosophy offers engineering education conceptual clarity, better articulation of epistemic practices, and critical tools for examining assumptions. Without such clarity, concepts risk misinterpretation, and integration efforts vary widely in quality. The honeycomb framework proposes a multifaceted definition of engineering, grounded in its interdisciplinary nature, problem diversity, and social dimensions. Engineering is not merely the application of science and mathematics; it generates technological knowledge, balances social, economic, technical, and environmental factors, and involves routine technical coordination and maintenance. Bucciarelli emphasized that engineering is “the negotiation of interest and proposals of different participants; hence the process is social and knowledge is socially constructed.”
At the core of the honeycomb model lies negotiation—internal reflection and external dialogue—mediating iterative design stages under constraints. This central cell connects adjoining hexagonal cells representing practices such as problem scoping, ideation, and evaluation. Problem scoping entails defining needs, constraints, and metrics through research and empathy-building. Ideation encourages fluency and avoids fixation via sketches, prototypes, and tinkering. Evaluation uses data to verify performance, employing experiments, simulations, and visualizations to support decisions.
The framework identifies six engineering inquiries: user-centered design (UCD), design-build-test (DBT), engineering science (ENS), engineering optimization (OPT), engineering analysis (EAN), and reverse engineering (REV). UCD prioritizes user needs and context, engaging all design stages. DBT applies and validates concepts through building and testing prototypes against clear requirements. ENS generates technological knowledge via controlled experiments on designed systems. OPT improves suboptimal systems through targeted evaluation and trade-off analysis. EAN relies on data and mathematical models to inform decisions without physical prototyping. REV dissects existing artifacts to understand, improve, or integrate systems.
Pedagogical translations adapt these inquiries for classroom use. UCD lessons immerse students in rich contexts, sometimes with real clients, to derive design criteria. DBT projects start with defined constraints, prompting students to prototype and test, often to reinforce science concepts. ENS lessons follow protocols to manipulate variables and observe effects on performance. OPT activities present a flawed system for systematic improvement within given parameters. EAN exercises focus on data analysis and modeling to make recommendations. REV tasks begin with unfamiliar artifacts, leading students to hypothesize, disassemble, and document functionality.
An analysis of 134 peer-reviewed K–12 engineering lessons revealed varied prevalence. DBT dominated across all grade levels, comprising 75% of elementary, 67% of middle school, and 50% of high school lessons. UCD accounted for 20% overall, more frequent at high school, while ENS appeared evenly but sparsely across levels. OPT, EAN, and REV were rare. Middle school curricula showed the widest variety, while elementary lessons concentrated on DBT and UCD.
The framework’s descriptive nature avoids prescribing quality, instead offering educators a lens to align lesson design with epistemological goals. It distinguishes philosophical underpinnings from pedagogical motives, preventing conflation of disciplinary practices with teaching strategies. By categorizing inquiries, it enables comparison of curricular impacts on learning and engagement, and invites expansion into underrepresented areas such as OPT and EAN, which could strengthen mathematics integration in engineering contexts.
Grounded in the philosophy of engineering, the honeycomb framework conceptualizes the discipline as creating, managing, and improving technological systems through negotiated trade-offs. It embraces engineering’s multifaceted nature—technical, social, and ethical—offering educators, researchers, and curriculum developers a structured yet flexible approach to representing the breadth of engineering in precollege education.
