Home

Research and academic work

How I use research

I often begin with a field and body of knowledge that the work requires. I search the relevant scholarship, compare how authors define the problem, separate observation from inference, and draw the relationships I think the evidence supports. I build upon conceptual models that I can test and challenge: against another source, against a counterexample, against a practical condition, or later against an implemented system.

I use scholarship to make assumptions visible, operationalize flows and phenomena, and build models. I identify tensions, frictions, and levers for improvement. I practice and revise the model when it does not fit the evidence. And I continue the research.

Evidence, assessment and judgment

Several graduate papers asked a version of the same question: what does the available evidence actually justify us saying?

Demotivated to Teach? — literature review. I investigated motivations relevant to men entering and remaining in teaching. I documented the search and screening process, separated gender-specific findings from broader worker-motivation research, and used self-determination theory's autonomy, competence, and relatedness as an organizing model while retaining material that did not fit it. The review found only limited teacher-specific evidence and did not establish a clear account of those dimensions among American teachers. It was a bounded course literature review, not a systematic review or participant study.

Observation Protocols — comparative assessment paper. I compared observation instruments by what they asked an observer to notice, how much inference the judgment required, the scale used, the observer's role, and whether the result supported feedback or an overall appraisal. Observable acts such as raised hands are different evidence from a judgment such as the quality of a learning environment. A weighted appraisal, peer observation, and an agreed informal focus therefore support different decisions and require different operating conditions. I compared existing materials; I did not administer or validate the instruments.

(In)authentic Assessments toward Authentic Learning. I compared written-question formats with performance, simulation, role-play, exhibition, and portfolio methods. I examined scoring effort, subjectivity, consistency, and the learning activity each method made possible, while keeping the observed output separate from the learning inferred from it. The paper made a literature-informed argument; it did not validate an assessment instrument.

Assessing Meritocratic Classes. I followed assessment results into later decisions about grade progression, retention, dropout, and judgments about teachers and schools. The paper examined how a measure can move through a system and acquire consequences beyond the original observation. It analyzed policy arguments; it did not evaluate an intervention I administered.

Together, these studies sharpened a distinction that also appears in my quality-assurance and current systems work: the record of an event, the evidence available about it, and the judgment made from that evidence are related but nonidentical things.

Read the selected academic evidence for method details and source limits.

Competence, participation and continuity

My undergraduate and graduate work also examined how people develop enough understanding to take responsibility, how different people participate in shared work, and what has to continue after one person leaves.

The three undergraduate capstone papers were explicitly theological. They examined New Testament ecclesiastical leadership, followership, mentoring, service, and community formation; one leadership paper expressly excluded business leadership from its scope. I organized part of the analysis around concepts, context, contact, and continuity: what people need to understand, the setting in which they act, the relationships through which they develop, and how responsibility continues after a central person is gone. Instructor feedback praised the research and illustrations while asking for more concrete steps and a workable plan.

The local application paper then adapted a cited plan–brief–execute–debrief cycle to a proposed neighborhood gathering. It specified resources, permissions, preparation, activity, and review, and asked whether attendance counts could actually establish the kind of development the plan cared about. The design remained an unimplemented draft.

In Family-Making Learning Theory, an ED500 essay, I modeled interacting relationships around a learner and proposed reciprocal teaching among people with different levels of experience. Its definition of family and its normative argument were explicitly theological. The model was philosophical and literature-informed; it was not empirically tested.

The professional value of these artifacts is not that a church or school model secretly proves a management method. They show a long-running inquiry into participation, development, differentiated responsibility, continuity, and the limits of what an observed outcome can establish.

Organizational design and operating conditions

The most complete graduate construction was a virtual technology high-school design. I treated the educational activity as only one part of an operating system that also needed staffing, learner support, access, governance, partnerships, accountability, and financing.

I proposed starting with one cohort replacing a specific partner school's course. Community projects and tangible deliverables would provide work for assessment, while instructors, project leaders, apprentices, universal-design practices, individualized plans, and tiered support would help participants engage with the work. Producing a useful deliverable would still leave a separate question about what each person had actually developed.

I organized intended development across thought processes, abilities, skills, and knowledge; applied the revised Bloom taxonomy; referenced the Occupational Therapy Practice Framework for activities of everyday civic life; and adapted Huwer and colleagues' DPaCK into Digitality Pedagogical Contact Knowledge, adding practical and subject expertise grounded in activity. These were model-building choices inside an academic design, not empirically validated constructs of my own.

The virtual setting still required physical and financial conditions. I worked through devices, connectivity, maintenance, places to meet or perform projects, recruitment and development of qualified instructors, governance, accreditation, outside services, startup cash flow, and review points for changing or stopping the initiative. The school was not launched; its educational outcomes and financial viability remain untested.

Personal Philosophy: Integrating Technology in Learning. In a separate paper, I modeled the relationships among learner, activity, and environment and connected technology choices to coaching, differentiation, facilitation, and learning through example.

A curriculum reflection on a published middle-school case asked a systems question that remains useful beyond education: improving information flow is not the same thing as improving the intended outcome. I considered whether integrating subjects through common themes changed what students were supposed to learn or mostly changed how information moved through the school. This was analysis of a published case, not a reform I implemented.

In Changing the Middle School Plan, I developed a twenty-step planning essay connecting a learning model to roles, assessment, developmental support, and case-based activity. The final step required reviewing and revising the preceding choices. It remained a researched plan rather than an implemented school change.

A subsequent Community Engagement Plan extended that design into communication with families and community participants, including feedback, language and cultural barriers, and practical support. The examples were proposed; I did not conduct or measure the conferences described.

A later policy essay traced how standards, funding, institutional choices, and classroom constraints interact across federal, state, and local levels. It was an explicitly theological and critical course argument, not a neutral policy evaluation or a record of reforms I delivered.

When the evidence changes the model

Early doctoral coursework produced one of the clearest examples of the research process I still use. I began a management-functional-area study expecting the literature to support a straightforward categorical list of business departments. It did not. Rather than force the sources into the expected structure, I revised the diagrams and reframed the inquiry around management functions, learning, and organizational context. The submission preserved unresolved questions instead of manufacturing a cleaner answer.

A separate problem-statement paper explored accountability in digital workspaces. It distinguished responsibility, accountability, and the assessment of accountability and proposed investigating relationships among consequences, evidence quality, and dialogue. That work produced a literature-based research question and rationale; it did not produce participant data, a completed dissertation, or an empirically validated instrument.

Other coursework compared rational, natural, and open-system perspectives; examined technology, organizational boundaries, and participation; and analyzed a case in which a factory, workforce, government, and union held conflicting goals and authority. Across the work, I used conceptual diagrams to make proposed relationships visible enough to critique and revise.

That constructive cycle now carries into my independent systems work: scholarly research can help build or challenge a conceptual model; MBSE principles can make selected relationships explicit as requirements, state, interfaces, constraints, evidence, authority, and views; software and AI/ML prototypes can then test parts of the logical structure. Those later implementations do not retroactively validate the academic models.

Degrees and assessed performance

Master of Education — Teaching & Learning: Leadership. Coursework included functional learning theory, Digitality Pedagogical Contact Knowledge (DPaCK), organizational learning, technological learning and learning technologies, digital transformation and cloud tech, policy and governance, and assessment.

Bachelor of Science — Religion: Biblical Studies and Theology. Coursework included regulatory and doctrinal interpretation, ethics and philosophy, accountability, leadership, and team formation.

Associate in Applied Science — Information Technology. Technical study complemented applied work in systems administration, networks, security, and service support.

Professional and technical education also included Distinguished Graduate and Honor Graduate recognition. I treat those results as evidence of strong performance in controlled academic and training settings. The operational record provides a separate test of what happened when I had to use the understanding in real systems, organizations, inspections, and delivery.

Selected academic evidence · Independent software and research · Career timeline

Organizational design and operating conditions

Inspect the source models

Inspect how I connected practical, teaching and digital knowledge

I used this adaptation to bring practical expertise into the same curriculum discussion as teaching and digital knowledge. Contact Knowledge intentionally names expertise grounded in the activity learners would undertake.

Digitality — digital-era abilities · Pedagogical — teaching and learning · Contact — practical and subject expertise grounded in activity · Tools — a region within Digitality. Pairwise regions: PDK pedagogical + digitality · DCK digitality + contact · PCK pedagogical + contact · DPaCK all three. Context: Home, Work and Leisure.
My school-design adaptation of Huwer and colleagues' framework. Contact Knowledge connects practical and subject expertise with teaching and digital knowledge; the overlap represents their combination in the proposed curriculum.
Inspect where I placed learning support

I used these relationships to locate support around the learner's encounter with practical work. An instructor could explain, demonstrate or change an obstructing condition; the design also had to account for the activity and environment.

Six directed relationships:
  • Learner → Activity and Activity → Learner
  • Learner → Environment and Environment → Learner
  • Activity → Environment and Environment → Activity
Support at the learner–activity interface: Resources · Strategies · Practices.
Learning relationships and support placement in my school-design proposal. Redrawn from the submitted paper's adaptations of Abdelaziz and of Salisbury and Irby. The relationships guided design questions; they do not measure learning.

Independent software and research

I use software and AI/ML prototyping to make parts of a longer research and modeling practice explicit enough to build, inspect, and test. The current formal prototype record covers a documented two-year development window; the questions and methods behind it developed through earlier technical, organizational, and scholarly work.

From research to constructed systems

Current prototype work

Developing case: this portfolio

Selected inspectable artifacts

Practical capabilities and limits

From research to constructed systems

I do not start with AI or code. I start with a function I am trying to understand. I use scholarly research and source evidence to compare definitions, challenge assumptions, and build or revise conceptual models. I then use model-based systems engineering principles to make selected relationships explicit as requirements, state, interfaces, constraints, evidence, authority, and views. Software and AI/ML prototypes give me another way to test whether those structures still make sense when I try to implement and use them.

That process is iterative. A source can force me to revise a model; implementation can expose a relationship the prose left vague; a failed check can reveal missing evidence, a missing capability, or a bad assumption. The objective is not to make the diagram look complete. It is to make the structure clear enough that the next claim, transition, or decision can be inspected and challenged.

The proprietary theory and implementation behind this work are not published on this employment site. I show the transferable practice and selected evidence without turning the portfolio into a product page.

Current prototype work

I have developed specifications and prototypes for work whose state, evidence, handoffs, and acceptance conditions should remain explicit rather than disappearing inside conversation. The current work includes structured records, workflow states, JSON schemas, and Python utilities for advancing state, compiling evidence, preparing handoffs, scaffolding schemas, and checking working notes.

Some consequences can be determined mechanically when the evidence and rules are sufficient. When they are not, the state should remain incomplete for a named reason: missing evidence, missing capability, a failed invariant or validation, an authority boundary, or unresolved judgment. A fluent explanation that something is complete is not a substitute for the implementation, evidence, validation, acceptance, or release state that would make it complete.

I also work on context and provenance across handoffs: what information should move, where it came from, what remains uncertain, and what authority travels with it.

I have also employed a SysML compiler prototype intended to translate modeled system intent between representations while retaining requirements, interfaces, constraints, relationships, and evidence references.

Developing case: this portfolio

This site remains a live case because one evidence field becomes several useful representations with different reader jobs and exposure levels. Recent work has moved beyond copy consistency into implemented shared object identity, separate public and invited projection state, interaction rules, rendered review, and package and release state. When those layers fail, I use the failure to change the structure or checks instead of only correcting the visible text.

Inspect selected software evidence

Selected inspectable artifacts

Research and conceptual models. The Research and academic work surface shows selected literature review, assessment analysis, organizational design, and model revision with their source and maturity limits.

Workflow and state prototypes. Current artifacts include specifications, schemas, Python utilities, modeled state transitions, evidence compilation, handoff structures, and partial compiler work. Source material remains private where publication would expose proprietary implementation.

Portfolio case study. This website is an example of how I build knowledge work software around practical information problems. The narratives, CV, timeline, and project library present views without becoming a different set of facts in each place. I use structured records, workflow state, schemas, Python utilities, and audience-specific views to keep their shared source and current state explicit while allowing each output to do a different job.

A smaller software-model correction. In one bounded intervention, I rejected a generated diagram that treated presentation views as if they defined the system's underlying structure. I directed a correction using shared records and explicit view membership. Retained reports record passing schema and reference checks and a controlled rendering comparison. That example remains useful because it is inspectable; its inspectability does not make it representative of the independent work as a whole. Read the selected excerpts.

Operational inspection. I am also building and testing a managed multi-model coding-assistant environment, including routing, caching, load balancing, throughput, and exception handling signals.

Practical capabilities and limits

  • Build and challenge conceptual models from scholarship, source evidence, and practice rather than treating research as an answer key.
  • Translate selected conceptual relationships into explicit requirements, state, interfaces, constraints, evidence, authority, and views for implementation or testing.
  • Keep actual workflow state distinct from a plausible narrative about progress.
  • Preserve source identity, provenance, uncertainty, and claim lineage across handoffs and derivative representations.
  • Make incomplete work explicit when evidence, capability, validation, authority, or judgment is unresolved.
  • Direct substantial AI-assisted implementation while keeping acceptance and authority tied to explicit evidence and rules rather than to fluent output.
  • Treat recurring corrections as candidate system refinements and test whether the new rule, validator, structure, or workflow actually reduces recurrence.
  • Inspect generated representations against the underlying model or source record and require revision when the representation changes the meaning.

This work comprises research, prototypes, personal operational use, and the ongoing development of live cases. The work builds upon my experience, technical training and credentials, and academic studies. The work also aims toward my future plans for doctoral research.

Contact Ray

Open Contact page