What Field Signals Are
Field Signals is an observation framework that helps workforce practitioners identify and name patterns in how AI is being adopted, governed, and applied across organizations.
Why "Field Signals"?
We use the word "signals" because they describe patterns that are visible, observable, and meaningful, but not deterministic. A signal invites interpretation; it does not dictate conclusions. A "field signal" is something that emerges from work in context, across diverse settings, not from a single vantage point.
These scenarios reflect real patterns practitioners across the workforce ecosystem are navigating today.
Maybe you're a workforce practitioner working across multiple partner organizations, workforce boards, employers, training providers, and noticing that each organization has made different calls about whether staff can use AI tools, which tools are approved, and how to use them. One partner organization has a comprehensive AI policy with approved tools for case notes and client communications. Another has banned all AI use until further notice. A third has no policy at all, leaving staff to make their own decisions about what's appropriate. You're trying to coordinate services across these partners, but you're navigating a patchwork of conflicting guidance where the same task might be encouraged in one organization, prohibited in another, and left to individual judgment in a third.
Maybe you're an HR director watching your AI applicant screening system filter resumes based on keywords, years of experience, and degree requirements, while your hiring managers are being trained to conduct competency-based interviews that assess problem-solving, adaptability, and leadership through behavioral questions. No one has clarified: Are we screening for credentials or capabilities? And if the AI is optimizing for one thing while interviews test for another, how do we know we're not systematically filtering out exactly the candidates who would perform best in the role?
Maybe you're a workforce training provider teaching traditional case management documentation, while your trainees are already using AI to write case notes, without understanding data privacy requirements, when AI-generated content needs human review, or how to maintain WIOA compliance with AI-assisted documentation.
Maybe you're a hiring manager watching your team spend their days reviewing AI-generated reports, correcting algorithmic errors, and supervising automated workflows, while the job description still lists "data analysis," "report writing," and "process documentation" as if employees were doing these tasks manually.
Below is a quick summary of patterns many practitioners notice across contexts.
You are noticing changes:
- Some teams use AI tools while others do not.
- Managers make different calls about what is allowed.
- Job descriptions have not changed, but the work has changed.
- Training programs feel misaligned with what is actually happening on the ground.
You do not yet have shared language to describe what is shifting or whether it matters.
Field Signals offer that language.
As artificial intelligence reshapes tasks, roles, and skill requirements, similar patterns are emerging across workforce systems. Field Signals describe these observable patterns.
What this is not
Field Signals are not metrics, evaluations, or prescriptions.
They are a shared language for noticing what is happening so practitioners and system leaders can ask better questions and respond intentionally.
Quick Example
In one organization, some managers encourage staff to use AI tools to draft reports, while others discourage any AI use at all. There is no written policy.
This pattern is a Field Signal. It reveals how AI is being adopted, governed, and experienced across the organization.
Example Signal
Manager-mediated signal
A pattern where access to or encouragement to use AI tools depends on individual supervisors rather than shared organizational guidance.
Why Field Signals Matter
Over time, these misalignments compound:
- Job seekers learn skills that don't match employer needs
- Practitioners develop workarounds that stay invisible to system designers
- Organizations make hiring and training decisions based on outdated assumptions
- Inequities emerge as some workers get support to adapt while others don't
Field Signals help surface these patterns early enough to act before they become entrenched in systems, policies, or organizational culture.
We're Building This Together
Field Signals are not static. They emerge from ongoing observation and shared learning across the workforce ecosystem. As AI adoption evolves and new patterns become visible, this framework will expand to reflect what practitioners are seeing on the ground.
If you are working in workforce development, training, HR, or systems leadership and recognize these patterns in your context, we invite you to join this learning community and help shape what Field Signals become.
Field Signals support thoughtful, human-centered workforce change by making patterns visible early enough to shape outcomes intentionally, together.
How to Use Field Signals
Field Signals support planning and dialogue in three ways:
For reflection
Notice which signals are present in your context and what they reveal about current practice.
Try asking: "Which of these signals do I recognize in our program? What does that tell me about where support may be needed?"
For alignment
Use signals as shared reference points across teams or organizations.
Example use: "In team meetings, reference specific signals when discussing AI adoption patterns. We are seeing a policy pacing signal where tools are in use but guidance has not caught up."
For strategy
Identify which signals, if addressed, would most support workforce goals.
Example approach: "If we are seeing a title proxy signal, what would skills-first hiring actually require? Who needs to be involved in that shift?"
Signals indicate conditions, not conclusions.
Signal Categories
Field Signals are organized into four categories that reflect different aspects of workforce systems.
Governance Signals
How AI use is being guided, encouraged, or constrained
Informal adoption signal
AI tools are used based on local norms or individual initiative rather than documented guidance.
Example:
Teams use various AI tools for different tasks, but there is no written policy, no shared training, and no clarity on data privacy boundaries.
Manager-mediated signal
Access to AI tools or encouragement to use them depends on individual supervisors or teams.
Example:
In one department, managers actively demonstrate AI tools and encourage experimentation. In another department, managers discourage AI use due to accuracy concerns. Staff experience depends entirely on who they report to. Staff in departments where AI is discouraged worry they're falling behind but don't know if asking about AI tools would be seen as pushing back on their manager's guidance.
Policy pacing signal
AI tools are in active use while governance guidance, documentation, or accountability structures are still developing.
Example:
Client-facing staff use AI to draft case notes and summarize interactions, but there is no documented review protocol, no clarity on liability, and no alignment with existing data governance policies.
What these signals suggest
Governance may be uneven, creating inconsistent expectations and accountability across roles or organizations. Without documented guidance, adoption patterns become difficult to see. This limits the ability to provide training, address risk, or ensure equitable access.
Skills Interpretation Signals
How skills are understood, defined, and applied
Title proxy signal
Job titles or credentials are used as stand-ins for skill requirements.
Example:
A job posting requires "five years as a case manager" rather than specifying skills like client assessment, crisis intervention, or referral coordination. This excludes candidates who have those exact skills from other contexts.
Static skills signal
Skills lists remain unchanged even as tasks within roles shift.
Example:
A training program for employment counselors still focuses on traditional interview techniques and paper intake forms, even though the role now includes using AI-powered case management systems, interpreting algorithm-generated job matches, and coaching clients on how to optimize their profiles for AI resume screening.
Transfer blind spot signal
Skills gained in one role, sector, or context are not recognized as transferable.
Example:
A customer service representative has strong de-escalation and problem-solving skills, but these are not recognized as relevant for career navigator roles because job titles do not align.
What these signals suggest
Skills visibility may be limited, constraining mobility and misaligning training or hiring decisions. When skills are defined by titles or credentials rather than capabilities, systems miss opportunities to recognize transferable skills and may reinforce unnecessary barriers.
Workforce Practice Signals
How decisions are made in day-to-day operations
Tool-first signal
Technology is introduced before workflows or use cases are clearly defined.
Example:
An organization purchases an AI-powered scheduling tool, but staff do not understand what problems it solves, how it fits their workflow, or who is responsible for training. Adoption is low and the tool creates more work than it saves.
Pilot isolation signal
Learning from pilots or experiments does not travel beyond the initial team.
Example:
One office successfully pilots an AI tool for intake documentation and develops useful protocols. Other offices hear about it informally but never receive documentation, training, or implementation support.
Workaround signal
Practitioners create informal processes to compensate for gaps in systems or guidance.
Example:
Case managers are asked to track client outcomes in a database that does not capture the information they actually need. They create parallel spreadsheets to do their real tracking, adding duplicative work.
What these signals suggest
Practice is adapting faster than systems, placing additional burden on frontline staff. When practitioners develop workarounds, it signals that existing systems are not meeting real needs but that knowledge often stays invisible to system designers and decision-makers.
Equity and Access Signals
How opportunity, risk, and support are distributed
Encouragement gap signal
Some roles or groups receive more encouragement or support to use AI tools than others.
Example:
Professional staff receive training on AI tools and are given time to experiment. Frontline staff hear about the tools in passing but receive no training, no protected time to learn, and no clarity on whether use is encouraged or discouraged.
Optional literacy signal
AI literacy is framed as optional rather than supported through training or guidance.
Example:
An organization announces that "AI tools are available for those who want to use them," but provides no baseline training on what the tools do, when they are appropriate to use, or how to evaluate outputs. Staff who have time and confidence experiment; others fall behind.
Opacity signal
Workers or clients are affected by AI-informed decisions without clear explanation or visibility.
Example:
A resume screening system flags certain candidates for review while others are filtered out, but applicants receive generic rejection messages with no explanation. Recruiters do not understand why certain candidates were prioritized and cannot explain the logic when asked.
What these signals suggest
Without intentional design, AI adoption may reinforce existing inequities rather than reduce them. Uneven access to training, encouragement, and understanding can create new divides between roles, and lack of transparency in AI-informed decisions can compound existing barriers.
Signals Often Appear in Clusters
Signals rarely appear in isolation. For example, an informal adoption signal (Governance) often appears alongside a policy pacing signal (also Governance) and an encouragement gap signal (Equity).
Recognizing these clusters can help identify systemic patterns rather than isolated issues.
When you notice multiple signals together, ask:
- What's the connecting thread?
- Which signal, if addressed, might have the most leverage?
- Who else needs to see this pattern?
Interpreting Signals Responsibly
Signals Are Descriptive, Not Evaluative
Finding signals in your organization doesn't mean:
- ✗ You're "behind" other organizations
- ✗ Leadership has failed
- ✗ Your approach is wrong
It means:
- ✓ You have visibility into patterns that might otherwise stay invisible
- ✓ You can respond thoughtfully before patterns become entrenched
- ✓ You're positioned to make informed decisions about where to focus
Field Signals should always be interpreted in context.
The presence of a signal does not imply poor intent or incorrect practice.
Signals often reflect:
- Resource constraints
- Legacy systems
- Policy timing
- Uneven access to training and support
- Competing organizational priorities
The purpose of naming signals is to make patterns visible early enough to respond thoughtfully, not to assign blame or suggest failure.
Why Context Matters
Example
A policy pacing signal may reflect rapid experimentation in one organization and governance gaps in another. The signal is the same, but the interpretation depends on context.
Using Signals Constructively
When you notice a signal:
- Describe what you are observing without judgment
- Ask what the signal reveals about current needs
- Consider who else needs to see the pattern
- Identify one concrete next step
Signals are most useful when they spark dialogue, not when they are used as evidence in arguments.
Getting Started: Three Ways to Use Field Signals This Week
Start small. You don't need to assess every signal or create a comprehensive plan. Here are three immediate ways to begin:
1. Individual reflection
Review the signal categories and note which 2-3 you recognize in your context. What do they reveal about current needs?
2. Team conversation
In your next staff meeting, share 1-2 signals and ask: "Are we seeing these patterns? What might they tell us?"
3. Strategic planning
When updating programs or policies, use signals as diagnostic questions: "Which signals would this change address?"
The goal isn't to eliminate all signals, it's to see patterns clearly enough to make informed choices.
Learning Across the Field
Organizations using Field Signals contribute to shared learning about how workforce systems are adapting to artificial intelligence.
When organizations share observed signals in aggregated and anonymized form, those patterns can surface common challenges and emerging practices. This shared learning supports reflection and coordination across the field, not evaluation or comparison.
How to Participate
What participation involves:
- Completing a brief signal assessment, approximately 15 minutes
- Optional participation in quarterly learning cohorts
- Receiving aggregated field insights twice per year
What you will get:
- A summary of signals present in your context
- How your patterns compare to field-wide trends
- Access to a community of practitioners working on similar challenges
- Early access to implementation resources as they are developed
Cost: Currently offered at no cost to participating workforce development organizations.
Get Started
If you are interested in contributing to this collective learning effort or would like to explore how Field Signals might support your organization's planning:
Or download the Field Signals Quick Reference Guide (PDF)
Additional Resources
- Field Signals Quick Reference (PDF)
- Signal Assessment Worksheet (PDF), Coming soon
- Responsible Use Statement
- Signal Library, Coming soon