# Job stories and user stories in agile product development

## Theoretical Foundations in Jobs-to-be-Done

The transition from traditional user stories to job stories within agile software development represents a fundamental paradigm shift in how organizations conceptualize, capture, and execute software requirements. This methodological shift is deeply rooted in the Jobs-to-be-Done (JTBD) theory, a theoretical framework that examines products, services, and software features through the lens of the underlying work that customers require them to perform [cite: 1, 2]. The core premise of the framework dictates that customers do not simply purchase products; rather, they "hire" products to accomplish specific objectives, solve situational struggles, or make progress in their lives [cite: 1, 3, 4]. 

### Origins and Evolution of the Theory

The philosophical origins of Jobs-to-be-Done can be traced to Theodore Levitt, a Harvard Business School professor and economist, who famously articulated the concept by stating that consumers do not desire to purchase a quarter-inch drill, but rather, they desire a quarter-inch hole [cite: 1, 5, 6]. This foundational assertion established the principle that consumers seek specific outcomes and progress over product attributes and features. The formalization of the JTBD theory into a structured business and product development methodology is largely attributed to Clayton Christensen, who expanded on these concepts in his research on disruptive innovation at Harvard Business School, notably in his book *The Innovator's Solution* [cite: 1, 5, 7]. 

Christensen’s models emphasized understanding the functional, social, and emotional dimensions of customer choices, moving beyond conventional market demographics or superficial product categories [cite: 3]. The theory argues that markets grow, evolve, and renew whenever customers have a "job" to be done and subsequently seek out a product or service to complete that job [cite: 2, 3]. A classic empirical example cited by Christensen involves a fast-food chain attempting to increase milkshake sales. Conventional demographic marketing failed to move the needle; however, JTBD research revealed that a significant portion of customers "hired" milkshakes in the morning to make a long, boring commute more interesting and to stave off mid-morning hunger. The job was not "to consume a dairy dessert," but rather "to provide engagement and sustenance during a commute" [cite: 7]. This distinction fundamentally alters how a product is designed, marketed, and evaluated against competitors.

### Divergent Methodological Frameworks

As the Jobs-to-be-Done theory matured and gained traction in software and product management circles, it bifurcated into distinct, yet complementary, methodological frameworks championed by different practitioners. These interpretations generally fall into two categories: Jobs-as-Activities and Jobs-as-Progress [cite: 6].

Anthony Ulwick introduced Outcome-Driven Innovation (ODI), an approach that primarily views Jobs-as-Activities. ODI treats JTBD as a highly structured, metric-driven process [cite: 1, 8]. Ulwick's methodology focuses on dissecting a customer's objective into a universal, step-by-step "job map" to identify unmet needs and rigorously measure where customers struggle the most [cite: 5, 8]. By quantifying these struggles, ODI directs product development and engineering resources toward areas where consumers are most severely underserved and thus most willing to pay a premium for better solutions [cite: 1, 5]. 

Conversely, Bob Moesta, who collaborated extensively with Christensen, developed the Demand-Side Sales framework and popularized the concept of "Switch Interviews," aligning closely with the Jobs-as-Progress interpretation [cite: 1, 6, 8]. Moesta’s approach emphasizes the timeline of customer decision-making—from the first thought of needing a change, to passive looking, active research, and the final decision to switch solutions [cite: 8, 9]. This interpretation relies heavily on qualitative psychological analysis, exploring the distinct emotional forces that drive a customer to abandon an existing solution in favor of a new one, rather than just mapping functional activities [cite: 7, 8].

## The Psychological Context of Customer Decisions

A foundational element of Moesta’s JTBD framework, which directly informs the construction of job stories, is the understanding of the psychological context surrounding a customer's decision to adopt a new product or software feature. This psychological ecosystem is formalized as the "Forces of Progress" [cite: 10, 11]. The JTBD framework posits that demand is not spontaneously generated; no user wakes up and inexplicably decides to purchase enterprise software or download a new application [cite: 10]. Instead, demand is the result of competing emotional and situational pressures acting upon the user simultaneously. 

The decision to switch to a new product occurs only when the forces of demand generation overcome the forces of demand reduction. To understand customer motivation, product designers must evaluate four distinct emotional forces that operate as vectors, either propelling a user toward a new solution or anchoring them to their current state [cite: 10, 11, 12, 13].

| Force of Progress | Directional Influence | Description and Psychological Impact |
| :--- | :--- | :--- |
| **Push** | Demand Generation (Away from current state) | Internal or external frustrations with the status quo. This force represents the friction, cost, or inadequacy of the current solution that makes the user unhappy and triggers the initial desire for change. |
| **Pull** | Demand Generation (Toward future state) | The magnetic attraction of a new solution. This consists of the user's visualization of a better life or improved workflow, combined with a preference for a specific product that promises to deliver that outcome. |
| **Anxiety** | Demand Reduction (Blocking the future state) | The uncertainty and fear associated with adopting something new. It manifests as *anxiety-in-choice* (fear of selecting the wrong product) and *anxiety-in-use* (fear that the product will be too difficult to learn or fail to perform). |
| **Habit** | Demand Reduction (Anchoring to current state) | The psychological comfort found in familiarity. Even if a current solution is suboptimal, existing routines (*habits-in-use*) or default purchasing behaviors (*habits-in-choice*) create inertia that prevents switching. |

*Table 1: The Four Forces of Progress governing customer decision-making within the Jobs-to-be-Done framework [cite: 10, 11, 12].*

### Forces of Demand Generation

The first force, **Push**, encompasses the internal or external frustrations a customer experiences with their current situation [cite: 10, 11]. People rarely seek change when they are content. A push occurs when circumstances render the current state untenable, creating the initial motivation to look for alternatives [cite: 10, 12]. For example, a business founder missing personal events because they are tethered to manual data reporting experiences a strong emotional and functional push away from their current software setup [cite: 4].

The second promoting force is **Pull**, which represents the promise and appeal of the new situation [cite: 11, 12]. The pull acts as the steering wheel that directs the user's motivation toward a specific destination [cite: 10]. Pull is heavily reliant on the user's ability to mentally simulate a better future; if a customer cannot successfully visualize how a new software feature will resolve their struggle and elevate their capabilities, they will lack the requisite motivation to change their behavior [cite: 10].

### Forces of Demand Reduction

Counteracting these demand generators are two potent blocking forces that product teams frequently underestimate. **Anxiety** represents the summation of all associated unknowns, uncertainties, and fears connected to the new solution [cite: 12]. Anxiety manifests in two distinct forms: *anxiety-in-choice* and *anxiety-in-use* [cite: 10, 11, 13]. Anxiety-in-choice occurs before a commitment is made, characterized by the fear of buyer's remorse or selecting an inadequate tool. Anxiety-in-use occurs post-adoption, involving nervousness about whether the product will continue to deliver satisfaction, whether it will integrate with existing workflows, or whether the learning curve will negate any promised time savings [cite: 10, 11].

The final force, **Habit** or inertia, is the psychological comfort found in the status quo [cite: 11, 12]. Even if the current solution is acknowledged as a chaotic or inefficient mess, it is a *familiar* mess [cite: 11]. The familiarity of existing routines (*habits-in-use*) or the default behavior of purchasing a known brand (*habits-in-choice*) acts as a powerful anchor preventing the customer from switching [cite: 10, 11]. For a product team utilizing JTBD, the strategic objective is to design software features, onboarding sequences, and marketing messaging that simultaneously amplify the push and pull while systematically neutralizing anxiety and accommodating or breaking existing user habits [cite: 4, 11, 12].

## The Mechanics of Agile Requirement Artifacts

To translate the philosophical insights of JTBD and the psychological nuances of the Forces of Progress into actionable software development practices, product organizations required an evolution in how they captured and communicated requirements to engineering teams. In traditional agile methodologies—such as eXtreme Programming (XP) and Scrum—the primary artifact for requirement capture has historically been the user story [cite: 14, 15, 16]. 

### The Anatomy and History of the User Story

The user story was originally conceived by Kent Beck as part of the eXtreme Programming methodology, with the intent of replacing exhaustive, monolithic functional requirement documents with lightweight placeholders designed to spark conversations between developers and business stakeholders [cite: 14, 15]. The concept was later refined and popularized by Mike Cohn, who helped establish it as the industry standard for agile requirements [cite: 14]. 

A user story operates on a highly standardized, three-part syntactic structure: "As a [role/persona], I want to [action/feature], so that [benefit/value]" [cite: 16, 17, 18]. This format deliberately forces product managers and development teams to explicitly identify the human persona for whom they are building a feature, ensuring a human-centered approach to software architecture and fostering empathy within the engineering organization [cite: 19, 20]. 

In modern development environments, user stories are operationalized within project management software such as Atlassian's Jira. Within Jira's hierarchical taxonomy, "Epics" represent large, overriding goals or overarching projects that span multiple sprints [cite: 21]. These Epics are broken down into individual User Stories, which serve as the fundamental units of value delivered in a single sprint. Finally, Stories are subdivided into technical "Tasks" or "Subtasks" that detail the precise engineering steps required for implementation [cite: 16, 21, 22]. 

User stories offer distinct advantages in complex enterprise environments where user roles are highly varied. When building software where understanding the nuanced differences between administrative personnel, standard users, financial auditors, and external clients is paramount to security and functionality, the user story format excels [cite: 23, 24]. By putting the specific user persona at the forefront of the requirement, the artifact prevents the development of isolated technical solutions that fail to address the unique workflow of the intended actor [cite: 19, 25].

### Structural Limitations of Persona-Driven Models

Despite their widespread adoption, user stories possess inherent structural limitations that become apparent as product complexity scales or as market dynamics shift. Critics note that when building consumer products or platforms for a largely homogeneous user base, the persona component becomes highly repetitive and analytically hollow [cite: 18, 23]. If every requirement in a sprawling product backlog begins with "As a user," "As a customer," or "As a shopper," the role clause ceases to provide any contextual value or insight to the engineering team [cite: 18, 23].

Furthermore, the user story format frequently leads product managers to prescribe precise functional solutions within the artifact itself. Because the syntax demands an "I want to [action]" clause, product managers often fill this space with exact UI or technical directives (e.g., "I want a dropdown menu," or "I want a dashboard") rather than illuminating the underlying problem [cite: 14, 17, 26]. This inadvertently restricts the engineering and design teams' ability to innovate, as they are tasked with building a pre-determined solution rather than solving a root cause [cite: 17, 27]. Finally, the traditional user story entirely lacks temporal context; it explains *who* wants a feature and *why*, but fails to articulate *when* the feature is required within the user's workflow [cite: 23, 27].

### Emergence and Syntax of the Job Story

To address the shortcomings of persona-driven requirements and prescriptive feature requests, the product team at Intercom, heavily influenced by the broader JTBD framework, popularized the concept of the Job Story as a viable alternative artifact [cite: 23, 28]. 

The job story abandons the emphasis on the user persona entirely, replacing it with an acute focus on the situational context and the underlying motivations driving the user [cite: 17, 24]. The job story utilizes a distinct syntactic structure: "When [situation], I want to [motivation], so I can [expected outcome]" [cite: 17, 29]. 

This formatting shift fundamentally alters the trajectory of product design. The "When [situation]" clause provides the triggering event or environmental context, answering the critical missing question of exactly *when* a feature is needed (e.g., "When an order is submitted" or "When I have only five minutes before my flight") [cite: 23, 30]. The "I want to [motivation]" clause replaces the prescriptive action of a user story, focusing instead on the psychological driver or immediate desire without dictating the technical execution [cite: 17, 27]. Finally, the "so I can [expected outcome]" clause defines the overarching progress the user is attempting to achieve, aligning directly with the core tenets of the JTBD theory by focusing on the destination rather than the vehicle [cite: 23, 26, 31].

## Syntactic Contrast and Implementation Context

The transition from user stories to job stories is not merely a semantic exercise in rewriting backlog tickets; it dictates the mental models utilized by designers, researchers, and engineers during product discovery and development [cite: 24, 27]. 

| Architectural Attribute | Traditional User Story Format | Job Story Format |
| :--- | :--- | :--- |
| **Primary Focus** | The individual persona, demographic, or role interacting with the system. | The situational context, environment, and the problem triggering the need. |
| **Standard Syntax** | As a [role], I want to [action], so that [benefit/gain]. | When [situation], I want to [motivation], so I can [expected outcome]. |
| **Opening Clause** | Identifies the actor (e.g., "As an admin..."). Entirely fails to capture timing or environmental triggers. | Identifies the trigger (e.g., "When an order is submitted..."). Deliberately ignores the actor's identity. |
| **Middle Clause** | Frequently prescribes a specific functional solution, UI element, or exact step to be taken. | Describes the underlying motivation and immediate need, leaving the technical solution open-ended for developers. |
| **Closing Clause** | Serves as a justification for the pre-determined functionality requested in the middle clause. | Defines the ultimate state of progress or business value the user wishes to reach. |
| **Optimal Use Case** | When distinct user roles have vastly different system permissions, unique workflows, or divergent needs. | When users share common environmental triggers or problems regardless of their demographic or professional profile. |

*Table 2: Structural and philosophical comparison of User Stories and Job Stories based on industry software development heuristics [cite: 17, 23, 24, 27].*

By framing requirements around the triggering event ("When") rather than the actor ("As a"), job stories prevent teams from making assumptions based on demographic personas [cite: 2, 17]. For example, a wealthy executive and a struggling college student may both encounter the exact same anxiety and motivation when attempting to complete a rapid mobile transaction in an area with poor connectivity [cite: 30]. Their demographic differences are entirely irrelevant to the engineering challenge, while their situational context and motivations are identical [cite: 24, 30].

Furthermore, the job story format is instrumental in avoiding the "Better Mousetrap" trap [cite: 4]. By focusing on the motivation rather than the action, teams avoid building features that customers do not actually want. A customer's desired outcome is never "I want to use accounting software"; their desired outcome is "I want to feel confident my financial books are compliant and accurate" [cite: 7, 26]. The software is merely a means to an end.

## Integration into Agile Ceremonies and Lifecycles

The integration of job stories into agile project management requires deliberate adjustments to standard ceremonies and artifacts. Modern software development relies heavily on frameworks like Scrum and Kanban to organize iterative delivery [cite: 32, 33, 34]. While broad adoption of agile methodologies is universally documented—with industry reports consistently showing that a vast majority of teams practice Scrum or hybrid-Scrum variations—specific, global statistical data quantifying the exact percentage adoption rate of job stories versus user stories remains unavailable or unmeasured in current macro-level enterprise research literature [cite: 29, 31, 33, 35]. Nevertheless, qualitative case studies, engineering playbooks, and procedural documentation indicate precisely how the artifact alters the development lifecycle.

### Product Discovery and Backlog Refinement

In agile environments, the product discovery phase is dedicated to mitigating risk by validating ideas, exploring market gaps, and determining if a problem is worth solving before committing to expensive engineering cycles [cite: 36, 37]. During this phase, product managers and UX researchers utilize JTBD frameworks to identify high-value opportunities. Through methodologies like the Opportunity Solution Tree, abstract customer feedback and survey data are structured into actionable insights [cite: 37]. Rather than generating feature requests, researchers conduct Switch Interviews to unearth the precise moments of frustration (the push) and the criteria for success (the pull) that trigger a user to abandon an old workflow [cite: 8, 12].

These insights are systematically distilled into job stories and placed into the product backlog [cite: 34]. During backlog refinement (or grooming)—a critical mid-sprint ceremony where the product owner and development team prepare upcoming work—job stories prove highly disruptive to traditional workflows [cite: 33, 38]. Because job stories highlight the motivation rather than a prescriptive feature, backlog refinement sessions transform from administrative sizing meetings into collaborative problem-solving exercises [cite: 25, 27]. Engineers and designers debate the optimal technical architecture to resolve the situational trigger, rather than simply estimating the effort required to build a pre-defined button or interface element [cite: 14, 25]. 

### Sprint Planning and Execution

During the sprint planning ceremony, the development team commits to a set of backlog items that align with the overarching sprint goal [cite: 33, 38, 39]. The use of job stories at this stage profoundly influences how tasks are broken down, assigned, and estimated. 

In a standard user story environment, estimating complexity (often using story points, planning poker, or T-shirt sizing) is relatively straightforward because the required action is highly specific [cite: 22, 39, 40]. However, because job stories deliberately leave the solution open-ended, the team must first agree on the proposed technical implementation during the planning phase before they can accurately assign story points [cite: 25, 26]. 

| Agile Ceremony | Traditional User Story Implementation | Job Story Implementation |
| :--- | :--- | :--- |
| **Product Discovery** | Developing detailed demographic personas; surveying users on what features they want to see built. | Conducting "Switch Interviews" to map the Forces of Progress; identifying triggers of non-consumption. |
| **Backlog Refinement** | Clarifying pre-defined features; adding acceptance criteria to functional actions. | Collaborative problem-solving; developers propose technical solutions to satisfy the motivational trigger. |
| **Sprint Planning** | Estimating the effort required to build the prescribed feature based on past velocity. | Debating the most efficient architectural approach to achieve the user's expected outcome before estimating effort. |
| **Daily Stand-up** | Reporting progress on specific technical tasks tied to the user story's functional requirement. | Evaluating progress against resolving the situational struggle defined in the job story. |
| **Sprint Review** | Demonstrating the completed feature functionality to stakeholders. | Demonstrating how the new increment successfully alleviates the user's previously mapped anxieties or pain points. |

*Table 3: The operational impact of shifting from User Stories to Job Stories across standard Agile Scrum ceremonies [cite: 8, 22, 25, 32, 33, 38, 39].*

To manage this ambiguity, high-performing agile teams often adapt their planning cadences. For example, some organizations decouple product discovery from delivery entirely, ensuring that job stories are supported by low-fidelity prototypes and validated assumptions prior to entering sprint planning [cite: 36, 37]. Organizations may also leverage customized tracking configurations within their issue-tracking software. In tools like Jira, while the "Story" issue type is standard, agile administrators configure custom fields to capture specific JTBD data points [cite: 40, 41, 42]. By mapping the "Forces of Progress" or the specific "Struggling Moment" directly into the ticket metadata, teams ensure that developers retain visibility into the psychological context throughout the execution phase, preventing them from losing sight of the core problem as they write code [cite: 26, 41, 42].

### Performance Measurement and Delivery Velocity

The shift to JTBD and job stories also alters how product teams measure success. While agile reporting metrics such as velocity, burndown charts, and cumulative flow diagrams remain essential for tracking output [cite: 34, 40], they do not measure business value. Organizations utilizing job stories shift their focus toward outcome-based metrics, such as Time-to-Market (TTM) and customer engagement [cite: 43, 44, 45]. 

Research indicates that reducing the development cycle time while improving product performance are often conflicting strategic objectives, forcing firms to explicitly consider the tradeoffs [cite: 46]. Job stories inherently reduce wasted development time by ensuring teams do not build features that fail to address a real customer struggle, thereby improving product-market fit and optimizing resource allocation [cite: 36, 47]. 

## Empirical Case Studies in Product Strategy

The theoretical superiority of the JTBD framework and job stories is frequently validated through empirical observation of highly successful technology enterprises, particularly within the rapidly scaling markets of Southeast Asia.

### Ecosystem Development at Gojek

Gojek, an Indonesian multi-service platform, achieved "decacorn" status (a valuation exceeding $10 billion) by adhering closely to the principles of product-market fit and situational problem-solving [cite: 47, 48]. Founded in 2010 by Nadiem Makarim as a simple call center connecting consumers with motorcycle taxis ("ojeks"), the company identified massive friction (pushes) in the existing transportation ecosystem: a lack of pricing transparency, severe safety concerns, and unpredictable availability [cite: 47]. 

Gojek's subsequent exponential growth into a dominant "super-app" demonstrates the large-scale application of JTBD thinking [cite: 47, 48, 49]. Instead of confining their product roadmap to the demographic persona of a "commuter," Gojek relentlessly analyzed the diverse situations their users faced daily. By launching a minimal viable product (MVP) called Go-Shop—an open-ended, on-demand delivery service—they generated fascinating behavioral data [cite: 47]. Through this MVP, Gojek discovered that 80% of users were hiring the service specifically to acquire food [cite: 47]. The situational job was not "ride-hailing," but rather "on-demand logistics for daily necessities." 

This insight led to the creation of GoFood, which rapidly captured over 75% of the Indonesian market share [cite: 47]. By focusing on the continuous resolution of localized, situational struggles—such as creating GoPay to serve an unbanked population where 66% of individuals lacked traditional bank accounts—Gojek built a sustainable ecosystem driven by user progress, eventually expanding to offer 22 distinct services within a single application [cite: 47, 48].

### Solving Acquisition Bottlenecks at Grab

Grab, a direct competitor to Gojek and the leading ride-hailing platform commanding 80% of the Southeast Asian market, utilized JTBD-aligned discovery methods to resolve critical business bottlenecks [cite: 45, 50]. The company identified a severe drop-off in its driver acquisition funnel, an issue that directly threatened their revenue model and operational scalability [cite: 45]. Data analysis revealed an alarming statistic: 60% of potential drivers were abandoning the sign-up process at the very first step, the initial information page [cite: 45]. 

Rather than viewing the problem purely through a technical lens or creating a generic user story (e.g., "As a potential driver, I want to sign up easily"), the product research team audited the entire situational flow to understand the anxieties and frustrations causing the massive bounce rate [cite: 45]. By mapping the exact steps and emotional hurdles potential drivers faced during onboarding, Grab redesigned the experience to directly alleviate those specific blockers. This contextual, motivation-driven approach resulted in a 32% reduction in drop-off rates and a 24% increase in user engagement within three months [cite: 45]. When user testing the new designs, the platform achieved an 86% satisfaction rate on a Likert scale, demonstrating measurable business impact achieved by resolving the underlying "job" of frictionless employment onboarding [cite: 45].

## Critiques, Demographics, and the Accessibility Deficit

While the job story effectively eliminates the constraints of demographic assumptions and solution-prescriptive requirements, this structural omission introduces significant and potentially dangerous risks to the software development lifecycle. The primary critique of the job story framework is its potential to obscure the distinct physical, cognitive, and technological realities of diverse user groups, leading to a profound accessibility deficit [cite: 23, 24, 51].

### The Erasure of Demographic Realities

By definition, job stories discard the "Role" clause ("As a user...") to focus purely on the situational trigger [cite: 18, 27]. The philosophical assumption underlying this format is that a user's motivation and expected outcome remain consistent regardless of their personal identity or capabilities [cite: 2, 24]. However, this framework structurally fails when the *method* of achieving the outcome is fundamentally restricted by a user's physical abilities or technological constraints [cite: 52, 53]. 

For example, the job story "When I am navigating a complex data dashboard, I want to quickly locate the quarterly revenue figures, so I can include them in my report" accurately describes the psychological intent of the user. Yet, it entirely erases the reality of a blind user relying on assistive technology, or a user with motor impairments who cannot utilize a mouse and relies entirely on keyboard navigation [cite: 53, 54, 55]. 

In contrast, a well-crafted accessibility user story specifically highlights the demographic requirement: "As a visually impaired user utilizing a screen reader, I want all data visualizations to have descriptive alt-text and structured data tables, so that I can accurately interpret the quarterly revenue figures" [cite: 52, 54]. Organizations like the Nielsen Norman Group and the World Wide Web Consortium (W3C) have consistently warned that designing for an idealized, generic user inevitably results in exclusionary software [cite: 53, 56]. When product managers rely solely on generic job stories, accessibility features are frequently relegated to non-functional requirements or ignored until post-development compliance checklists, rather than being integrated into the core user experience [cite: 51, 54].

### Legal and Compliance Risks

The failure to explicitly capture accessibility requirements within agile artifacts exposes organizations to severe legal, financial, and reputational liabilities. In the United States, Section 508 of the Rehabilitation Act mandates that all electronic and information technology procured, developed, or used by federal agencies be accessible to people with disabilities [cite: 57, 58]. This legislation effectively forces private sector vendors operating in the federal space to comply with the Web Content Accessibility Guidelines (WCAG) version 2.0 or 2.1 at the AA level [cite: 58, 59]. 

The WCAG framework outlines technical specifications based on four foundational principles, known by the acronym POUR: digital content must be Perceivable, Operable, Understandable, and Robust [cite: 59]. Furthermore, the imminent enforcement of the European Accessibility Act (EAA) in 2025 will impose stringent accessibility mandates on digital products across the European Union, extending compliance risks globally [cite: 60].



The volume of litigation surrounding digital accessibility is accelerating rapidly. In 2024 alone, plaintiffs filed over 4,000 lawsuits relating to digital properties under the Americans with Disabilities Act (ADA) in the United States [cite: 60]. While federal cases saw a slight decline, state-level lawsuits in jurisdictions like New York and California surged as plaintiffs leveraged state-specific laws [cite: 60]. 

Crucially, 40% of these cases—nearly one in four lawsuits—were repeat offenses targeted at organizations that had previously been sued but failed to rectify their underlying accessibility barriers [cite: 60].

[image delta #1, 0 bytes]

 When agile teams rely exclusively on persona-less job stories that gloss over how different users interact with technology, they risk deploying software that violates these civil rights mandates, triggering costly remediation cycles and exposing the enterprise to chronic litigation [cite: 54, 60].

### Vicarious Discrimination and Professional Burnout

The friction between rapid agile delivery frameworks (which prioritize speed and continuous integration) and the necessity of inclusive design places an immense, often unmeasured burden on accessibility professionals embedded within product teams [cite: 35, 51]. When accessibility is not structurally woven into sprint planning via explicit requirements, these professionals face what is known as "vicarious discrimination"—the emotional residue and exhaustion of constantly witnessing, and fighting against, the exclusion of marginalized users [cite: 61]. 

Accessibility professionals effectively become witnesses to the pain and frustration of discrimination survivors [cite: 61]. The expectation to act as the sole barrier against inaccessible deployments—often in environments where leadership prioritizes shipping features over fixing critical usability bugs—frequently leads to high turnover and severe professional burnout [cite: 51, 61]. Furthermore, current research highlights that algorithmic bias in AI tools and automated systems often exacerbates these barriers, making it even more difficult for disabled individuals to participate equally in the labor market [cite: 62, 63]. Replacing explicit user personas with generic situational stories threatens to institutionalize this oversight.

## Reconciling Frameworks through Hybrid Methodologies

To reconcile the undeniable strategic benefits of the JTBD framework with the ethical and legal imperatives of inclusive design, mature product organizations are increasingly adopting hybrid methodologies [cite: 23, 25]. 

Practitioners recommend utilizing job stories during high-level product discovery, roadmap planning, and epic creation [cite: 17, 27]. At this strategic altitude, the job story excels at identifying broader market opportunities, mapping the Forces of Progress, and ensuring the product organization is solving real, validated problems rather than building unwanted features [cite: 17, 26]. 

However, as those high-level epics are broken down into granular deliverables for sprint execution, teams must reintroduce demographic constraints. This is achieved either by integrating specific accessibility user stories into the backlog alongside the job stories, or by embedding strict, WCAG-compliant accessibility requirements directly into the Definition of Done and the Acceptance Criteria of the job stories themselves [cite: 15, 52, 54]. For example, establishing an acceptance criteria stating, "All text must have a contrast ratio of at least 4.5:1 against its background" ensures compliance regardless of the artifact used [cite: 52]. By blending the motivational context and causal logic of the job story with the rigid physical constraints and empathy of the user story, agile development teams can build software that is both highly relevant to the market and fundamentally inclusive for all users.

## Conclusion

The transition from user stories to job stories reflects a necessary evolution in how software organizations understand product-market fit, moving away from superficial demographic assumptions toward a deeper, causal understanding of user motivation. By leveraging the theoretical underpinnings of the Jobs-to-be-Done framework—specifically the psychological dynamics of Push, Pull, Habit, and Anxiety—agile teams can align their engineering efforts with the precise situational realities that drive consumer behavior. 

However, this methodological shift is not without inherent risk. The complete removal of the user persona can blind development teams to critical accessibility requirements, inadvertently excluding marginalized populations and exposing organizations to severe legal liability. Ultimately, the most effective agile organizations do not view user stories and job stories as an ideological binary. Instead, they treat them as complementary analytical tools—leveraging job stories to discover what to build, and user stories to ensure that what is built can be utilized by everyone.

## Sources

1. [vgeraldine.medium.com/growth-case-study-gojek-fc60555dcce4](https://vgeraldine.medium.com/growth-case-study-gojek-fc60555dcce4)
2. [ejournal.joninstitute.org/index.php/ProBisnis/article/download/529/479](https://ejournal.joninstitute.org/index.php/ProBisnis/article/download/529/479)
3. [ijc.ilearning.co/index.php/ATM/article/view/2464](https://ijc.ilearning.co/index.php/ATM/article/view/2464)
4. [www.researchgate.net/publication/371813122_The_Transitioning_Experiences_from_Traditional_to_Agile_Project_Management_A_Case_of_an_Information_Technology_Department_of_a_Private-Owned_Financial_Institution_in_Cebu_City](https://www.researchgate.net/publication/371813122_The_Transitioning_Experiences_from_Traditional_to_Agile_Project_Management_A_Case_of_an_Information_Technology_Department_of_a_Private-Owned_Financial_Institution_in_Cebu_City)
5. [www.materialplus.io/sg/perspectives/latest-agile-trends-in-2025-and-beyond](https://www.materialplus.io/sg/perspectives/latest-agile-trends-in-2025-and-beyond)
6. [seibert.group/products/blog/jira-custom-fields-guide/](https://seibert.group/products/blog/jira-custom-fields-guide/)
7. [blog.isostech.com/jira-custom-fields-the-complete-guide-2025](https://blog.isostech.com/jira-custom-fields-the-complete-guide-2025)
8. [community.atlassian.com/forums/App-Central-articles/How-to-Implement-Agile-in-Jira-and-Actually-Make-It-Work/ba-p/3051793](https://community.atlassian.com/forums/App-Central-articles/How-to-Implement-Agile-in-Jira-and-Actually-Make-It-Work/ba-p/3051793)
9. [www.atlassian.com/agile/project-management/epics-stories-themes](https://www.atlassian.com/agile/project-management/epics-stories-themes)
10. [www.easyagile.com/blog/agile-ceremonies](https://www.easyagile.com/blog/agile-ceremonies)
11. [spiralscout.com/blog/discovery-phase-is-key-to-successful-product-development](https://spiralscout.com/blog/discovery-phase-is-key-to-successful-product-development)
12. [neemz.medium.com/project-scoping-for-product-discovery-8d7f2aec61cd](https://neemz.medium.com/project-scoping-for-product-discovery-8d7f2aec61cd)
13. [usersnap.com/blog/product-discovery-techniques-methods/](https://usersnap.com/blog/product-discovery-techniques-methods/)
14. [www.researchgate.net/publication/271990327_The_Impact_of_Development_Speed_on_New_Product_Success_A_Meta-Analysis](https://www.researchgate.net/publication/271990327_The_Impact_of_Development_Speed_on_New_Product_Success_A_Meta-Analysis)
15. [opinov8.com/insights/speed-in-product-development-market-success/](https://opinov8.com/insights/speed-in-product-development-market-success/)
16. [m.economictimes.com/news/international/us/are-quiet-achievers-doomed-the-unfair-reality-of-office-visibility-bias/articleshow/131114050.cms](https://m.economictimes.com/news/international/us/are-quiet-achievers-doomed-the-unfair-reality-of-office-visibility-bias/articleshow/131114050.cms)
17. [pmc.ncbi.nlm.nih.gov/articles/PMC11872222/](https://pmc.ncbi.nlm.nih.gov/articles/PMC11872222/)
18. [www.hrdive.com/news/job-seekers-frustrated-by-opaque-impersonal-hiring-process/819898/](https://www.hrdive.com/news/job-seekers-frustrated-by-opaque-impersonal-hiring-process/819898/)
19. [www.weforum.org/stories/2022/12/disability-inclusion-is-not-discretionary/](https://www.weforum.org/stories/2022/12/disability-inclusion-is-not-discretionary/)
20. [arxiv.org/html/2508.18492v1](https://arxiv.org/html/2508.18492v1)
21. [aktiasolutions.com/user-stories-vs-job-stories-comparative-dive/](https://aktiasolutions.com/user-stories-vs-job-stories-comparative-dive/)
22. [www.intercom.com/blog/jobs-to-be-done-book/](https://www.intercom.com/blog/jobs-to-be-done-book/)
23. [jtbd.info/the-forces-of-progress-4408bf995153](https://jtbd.info/the-forces-of-progress-4408bf995153)
24. [www.mountaingoatsoftware.com/blog/job-stories-offer-a-viable-alternative-to-user-stories](https://www.mountaingoatsoftware.com/blog/job-stories-offer-a-viable-alternative-to-user-stories)
25. [www.effectory.com/knowledge/top-employee-surveys-2023/](https://www.effectory.com/knowledge/top-employee-surveys-2023/)
26. [www.productleadership.com/blog/power-of-metrics-in-product-management/](https://www.productleadership.com/blog/power-of-metrics-in-product-management/)
27. [www.gallup.com/workplace/649487/world-largest-ongoing-study-employee-experience.aspx](https://www.gallup.com/workplace/649487/world-largest-ongoing-study-employee-experience.aspx)
28. [www.mckinsey.com/~/media/mckinsey/business%20functions/people%20and%20organizational%20performance/our%20insights/the%20state%20of%20organizations%202023/the-state-of-organizations-2023.pdf](https://www.mckinsey.com/~/media/mckinsey/business%20functions/people%20and%20organizational%20performance/our%20insights/the%20state%20of%20organizations%202023/the-state-of-organizations-2023.pdf)
29. [www.forbes.com/councils/theyec/2023/03/29/the-most-important-employee-metrics-that-can-make-your-business-better-in-2023/](https://www.forbes.com/councils/theyec/2023/03/29/the-most-important-employee-metrics-that-can-make-your-business-better-in-2023/)
30. [www.konrad.com/research/user-stories](https://www.konrad.com/research/user-stories)
31. [sherifmansour.medium.com/how-weve-destroyed-user-stories-8b36120645c6](https://sherifmansour.medium.com/how-weve-destroyed-user-stories-8b36120645c6)
32. [www.section508.gov/develop/user-stories/](https://www.section508.gov/develop/user-stories/)
33. [www.meegle.com/en_us/topics/user-story/user-story-acceptance-criteria-for-accessibility](https://www.meegle.com/en_us/topics/user-story/user-story-acceptance-criteria-for-accessibility)
34. [www.agilebusiness.org/dsdm-project-framework/requirements-and-user-stories.html](https://www.agilebusiness.org/dsdm-project-framework/requirements-and-user-stories.html)
35. [asana.com/resources/agile-scrum-ceremonies](https://asana.com/resources/agile-scrum-ceremonies)
36. [microsoft.github.io/code-with-engineering-playbook/agile-development/ceremonies/](https://microsoft.github.io/code-with-engineering-playbook/agile-development/ceremonies/)
37. [www.atlassian.com/agile/project-management/user-stories](https://www.atlassian.com/agile/project-management/user-stories)
38. [www.avion.io/blog/agile-ceremonies/](https://www.avion.io/blog/agile-ceremonies/)
39. [medium.com/@StarAgileScrumZone/5-real-sprint-planning-examples-that-actually-worked-4c8586ca2480](https://medium.com/@StarAgileScrumZone/5-real-sprint-planning-examples-that-actually-worked-4c8586ca2480)
40. [www.karneetk.com/grab-case-study](https://www.karneetk.com/grab-case-study)
41. [vgeraldine.medium.com/growth-case-study-gojek-fc60555dcce4](https://vgeraldine.medium.com/growth-case-study-gojek-fc60555dcce4)
42. [savvycomsoftware.com/blog/case-study-grab/](https://savvycomsoftware.com/blog/case-study-grab/)
43. [ejournal.joninstitute.org/index.php/ProBisnis/article/download/529/479](https://ejournal.joninstitute.org/index.php/ProBisnis/article/download/529/479)
44. [www.ptengine.com/blog/business-strategy/what-brands-can-learn-from-gojeks-marketing-and-growth-strategies/](https://www.ptengine.com/blog/business-strategy/what-brands-can-learn-from-gojeks-marketing-and-growth-strategies/)
45. [www.nngroup.com/articles/accessibility-inclusivity-study-guide/](https://www.nngroup.com/articles/accessibility-inclusivity-study-guide/)
46. [www.nngroup.com/reports/topic/accessibility/](https://www.nngroup.com/reports/topic/accessibility/)
47. [www.hbs.edu/bigs/harvard-research-women-workplace-advancement](https://www.hbs.edu/bigs/harvard-research-women-workplace-advancement)
48. [medium.com/inclusion-insights/are-diversity-policies-useless-e9fcd9845939](https://medium.com/inclusion-insights/are-diversity-policies-useless-e9fcd9845939)
49. [www.nngroup.com/articles/ux-challenges/](https://www.nngroup.com/articles/ux-challenges/)
50. [mrcet.com/downloads/digital_notes/CSE/III%20Year/CS/AGILE%20METHODOLOGIES(1).pdf](https://mrcet.com/downloads/digital_notes/CSE/III%20Year/CS/AGILE%20METHODOLOGIES(1).pdf)
51. [www.researchgate.net/publication/323449852_Jobs-to-be-Done_Oriented_Requirements_Engineering_A_Method_for_Defining_Job_Stories](https://www.researchgate.net/publication/323449852_Jobs-to-be-Done_Oriented_Requirements_Engineering_A_Method_for_Defining_Job_Stories)
52. [www.scribd.com/document/705192494/designing-autonomous-teams-and-services](https://www.scribd.com/document/705192494/designing-autonomous-teams-and-services)
53. [medium.com/@stefanw/food-agile-thought-437-dunbars-number-age-of-product-com-3eb7201b9191](https://medium.com/@stefanw/food-agile-thought-437-dunbars-number-age-of-product-com-3eb7201b9191)
54. [medium.com/@mustafa.bohra20/agile-project-management-9650eeda8de5](https://medium.com/@mustafa.bohra20/agile-project-management-9650eeda8de5)
55. [www.ubabelgium.be/l/nl/library/download/urn:uuid:c26fb7c9-83e1-4851-94ce-b40e1830a6a9/whitepaper_how+to+build+a+successful+employer+brand_digital.pdf?format=save_to_disk](https://www.ubabelgium.be/l/nl/library/download/urn:uuid:c26fb7c9-83e1-4851-94ce-b40e1830a6a9/whitepaper_how+to+build+a+successful+employer+brand_digital.pdf?format=save_to_disk)
56. [103.203.175.90:81/fdScript/RootOfEBooks/E%20Book%20collection%20-%202026%20-%20J/AI%20DS%20ML/Beyond%20AI.pdf](http://103.203.175.90:81/fdScript/RootOfEBooks/E%20Book%20collection%20-%202026%20-%20J/AI%20DS%20ML/Beyond%20AI.pdf)
57. [www.engageemployee.com/employee-agenda](https://www.engageemployee.com/employee-agenda)
58. [www.w3.org/community/reports/](https://www.w3.org/community/reports/)
59. [sumatosoft.com/services/business-analysis](https://sumatosoft.com/services/business-analysis)
60. [builtin.com/articles/jobs-to-be-done-framework](https://builtin.com/articles/jobs-to-be-done-framework)
61. [gopractice.io/product/jobs-to-be-done-the-theory-and-the-frameworks/](https://gopractice.io/product/jobs-to-be-done-the-theory-and-the-frameworks/)
62. [mrx.sivoinsights.com/blog/top-frameworks-that-support-jobs-to-be-done-jtbd-thinking](https://mrx.sivoinsights.com/blog/top-frameworks-that-support-jobs-to-be-done-jtbd-thinking)
63. [gonogo.team/jobs-to-be-done](https://gonogo.team/jobs-to-be-done)
64. [businessofsoftware.org/deep-dive-jtbd/](https://businessofsoftware.org/deep-dive-jtbd/)
65. [customlytics.com/wp-content/uploads/2020/02/Mobile_Developers_Guide_18th_edition_web-3.pdf](https://customlytics.com/wp-content/uploads/2020/02/Mobile_Developers_Guide_18th_edition_web-3.pdf)
66. [www.w3.org/TR/2021/DNOTE-wcag-3.0-explainer-20211207/](https://www.w3.org/TR/2021/DNOTE-wcag-3.0-explainer-20211207/)
67. [repository.library.noaa.gov/view/noaa/46457/noaa_46457_DS1.pdf](https://repository.library.noaa.gov/view/noaa/46457/noaa_46457_DS1.pdf)
68. [www.digitalrhetoriccollaborative.org/2016/11/21/ccdp-as-a-case-study-for-digital-publishing-efforts/](https://www.digitalrhetoriccollaborative.org/2016/11/21/ccdp-as-a-case-study-for-digital-publishing-efforts/)
69. [www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=5131367&FileName=36C77619R0010-001.pdf](https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=5131367&FileName=36C77619R0010-001.pdf)
70. [www.mountaingoatsoftware.com/blog/job-stories-offer-a-viable-alternative-to-user-stories](https://www.mountaingoatsoftware.com/blog/job-stories-offer-a-viable-alternative-to-user-stories)
71. [medium.com/@KonstantinPM/what-is-the-difference-between-user-story-and-job-story-9a53234af947](https://medium.com/@KonstantinPM/what-is-the-difference-between-user-story-and-job-story-9a53234af947)
72. [ehandbook.com/job-stories-vs-user-stories-the-misguided-debate-90f8b96eaee6](https://ehandbook.com/job-stories-vs-user-stories-the-misguided-debate-90f8b96eaee6)
73. [www.withintent.com/blog/user-stories-vs-job-stories/](https://www.withintent.com/blog/user-stories-vs-job-stories/)
74. [contentdesign.london/blog/the-difference-between-job-stories-and-user-stories](https://contentdesign.london/blog/the-difference-between-job-stories-and-user-stories)
75. [brianrhea.com/customer-acquisition-customer-retention/](https://brianrhea.com/customer-acquisition-customer-retention/)
76. [jtbd.info/the-forces-of-progress-4408bf995153](https://jtbd.info/the-forces-of-progress-4408bf995153)
77. [www.mozestudio.com/journal/practical-guide-to-jobs-to-be-done](https://www.mozestudio.com/journal/practical-guide-to-jobs-to-be-done)
78. [spatialrd.com/spatial-thinking/107/jobs-theory-and-four-forces-progress](http://spatialrd.com/spatial-thinking/107/jobs-theory-and-four-forces-progress)
79. [customercentricllc.com/the-wheel-of-progress-overview](https://customercentricllc.com/the-wheel-of-progress-overview)
80. [sheribyrnehaber.medium.com/2026-accessibility-hiring-looks-busy-yet-the-patterns-show-underlying-weakness-239f04085ff6](https://sheribyrnehaber.medium.com/2026-accessibility-hiring-looks-busy-yet-the-patterns-show-underlying-weakness-239f04085ff6)
81. [www.section508.gov/blog/Barriers-to-Accessibility-Stories-from-Our-Community/](https://www.section508.gov/blog/Barriers-to-Accessibility-Stories-from-Our-Community/)
82. [arxiv.org/html/2508.18492v1](https://arxiv.org/html/2508.18492v1)
83. [www.eeoc.gov/meetings/meeting-january-31-2023-navigating-employment-discrimination-ai-and-automated-systems-new/moore](https://www.eeoc.gov/meetings/meeting-january-31-2023-navigating-employment-discrimination-ai-and-automated-systems-new/moore)
84. [medium.com/swlh/the-accessibility-profession-can-be-stressful-exhausting-and-frustrating-54d62a93df10](https://medium.com/swlh/the-accessibility-profession-can-be-stressful-exhausting-and-frustrating-54d62a93df10)
85. [www.scribd.com/document/705192494/designing-autonomous-teams-and-services](https://www.scribd.com/document/705192494/designing-autonomous-teams-and-services)
86. [mrcet.com/downloads/digital_notes/CSE/III%20Year/CS/AGILE%20METHODOLOGIES(1).pdf](https://mrcet.com/downloads/digital_notes/CSE/III%20Year/CS/AGILE%20METHODOLOGIES(1).pdf)
87. [www.researchgate.net/publication/323449852_Jobs-to-be-Done_Oriented_Requirements_Engineering_A_Method_for_Defining_Job_Stories](https://www.researchgate.net/publication/323449852_Jobs-to-be-Done_Oriented_Requirements_Engineering_A_Method_for_Defining_Job_Stories)
88. [uxplaybook.org/ux-glossary](https://uxplaybook.org/ux-glossary)
89. [www.id.ac.nz/blog/the-ultimate-ux-glossary-for-2025-and-beyond](https://www.id.ac.nz/blog/the-ultimate-ux-glossary-for-2025-and-beyond)
90. [www.withintent.com/blog/user-stories-vs-job-stories/](https://www.withintent.com/blog/user-stories-vs-job-stories/)
91. [www.mountaingoatsoftware.com/blog/job-stories-offer-a-viable-alternative-to-user-stories](https://www.mountaingoatsoftware.com/blog/job-stories-offer-a-viable-alternative-to-user-stories)
92. [community.atlassian.com/forums/Jira-articles/Difference-and-use-cases-of-Jira-issue-types-Epic-vs-Story-vs/ba-p/1655157](https://community.atlassian.com/forums/Jira-articles/Difference-and-use-cases-of-Jira-issue-types-Epic-vs-Story-vs/ba-p/1655157)
93. [titanapps.io/blog/how-to-write-user-stories-in-jira](https://titanapps.io/blog/how-to-write-user-stories-in-jira)
94. [deviniti.com/blog/enterprise-software/jira-user-story-template/](https://deviniti.com/blog/enterprise-software/jira-user-story-template/)
95. [jtbd.info/the-forces-of-progress-4408bf995153](https://jtbd.info/the-forces-of-progress-4408bf995153)
96. [www.aakashg.com/jobs-to-be-done-template/](https://www.aakashg.com/jobs-to-be-done-template/)
97. [uxdesign.cc/creating-a-jobs-to-be-done-statement-is-easy-getting-the-data-to-support-it-is-not-299bcabc5dcf](https://uxdesign.cc/creating-a-jobs-to-be-done-statement-is-easy-getting-the-data-to-support-it-is-not-299bcabc5dcf)
98. [www.christenseninstitute.org/theory/jobs-to-be-done/](https://www.christenseninstitute.org/theory/jobs-to-be-done/)
99. [www.minervamktg.com/post/get-more-from-your-marketing-with-the-jtbd-framework](https://www.minervamktg.com/post/get-more-from-your-marketing-with-the-jtbd-framework)
100. [www.wcag.com/compliance/section-508/](https://www.wcag.com/compliance/section-508/)
101. [www.nationaldisabilityinstitute.org/wp-content/uploads/2025/01/intersectionoftechnologydisabilityandworkerrights2024report.pdf](https://www.nationaldisabilityinstitute.org/wp-content/uploads/2025/01/intersectionoftechnologydisabilityandworkerrights2024report.pdf)
102. [accessibe.com/wp-content/uploads/2025/12/legal-report.pdf](https://accessibe.com/wp-content/uploads/2025/12/legal-report.pdf)
103. [blog.usablenet.com/2024-digital-accessibility-lawsuit-report-relased-insights-for-2025](https://blog.usablenet.com/2024-digital-accessibility-lawsuit-report-relased-insights-for-2025)
104. [digitalcommons.cwu.edu/cgi/viewcontent.cgi?article=1373&context=etd](https://digitalcommons.cwu.edu/cgi/viewcontent.cgi?article=1373&context=etd)

**Sources:**
1. [gopractice.io](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEUYX0T4gb2-ivzO3bEC7Bm6lbdVKR_OAL9P1tbGsjKaA__hmzwYJRDDAzzaJjd0VSofPz-5TWGZWiSa9Ow7frvlbVRpHpoEaPodWKhxQwRcaQNEgubRnrtwvvuQBMY2ODwIAPIIN2uzzMzZUkob0jwNzhkBqWdbCVqervZHBwQtwEo)
2. [uxplaybook.org](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQF0m7HouU5x-xj4ASIAwZ-xpA8ATsYot0esJuIMhbycXIrrQsTbU2jLnWJKyqx5ApdQyOH9G4uIIKK3D0_7JSIJ4nejz2HOtRpxJScy_IfMt9heS2nX-ShB)
3. [christenseninstitute.org](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHl9m6Z-KrrouZyWFouSRfDJH8HD2yQtldadrxHyXKRjc9bSHGOVGacOMbdRzoB__a8_fWqjHvhqL2abPFhT78E8XQlk4t74k5O6IYAdqCQuYgI9xGvacMek-FwGHQ9eiEm626wIJiS-YVdVUggC98ufzA=)
4. [minervamktg.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEz8VKkL3c3nFnSfb6IR-EFm5wbzWYKqZcuaJPUCJ17ssw7C3KMqYki5NsQvwYSvtTzurSKoTk2D5JzX5wUFMC4rauHPgeSvUsVccRfK--PpsIircOsO_xJ-nEDx_SVZP9rCvFuXyE5zWY5xmOrwbOH-x6Sy1bPMnsI-qDQh4VS02NtcqpwbagbZ1t_)
5. [builtin.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQFPte-cNf3yZI-qh5z349DCbeEMRY0DGjR4my6ssLooEreFWCdISunbRb8sgjuFUxGq3RJMg_Q3elPxOHgsTxWwMyQaW-xt0CYhXXntDnHi9WZxQsMB04W32uBr391bU-7h1VCOKv8woGuBvDE=)
6. [businessofsoftware.org](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGViN-66covUUHqmXbkJghVp-FtUv728d1xl4iMhXLR85hF8Lfnu-rzV6tGVyHcnYON2qNFTxZVJh0wzLbgCDboNUqQgeNGJEDFweqDE0UtwuYvuisUFDKP0ZZaehYr6Tq3Em-J)
7. [gonogo.team](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQH1Bk7GKAxfsSzLgQpVuyapyMDekMW1_-JAyHv2alygjR0FbqY_2lrU4-KvBvd1Ve_XNjdxlLZzz2B5NiuKlfVwT5vujDfR0z9aswakcOA2w7C_IURW72ws4A==)
8. [sivoinsights.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQG8IiiGRem7LLbYZJIEPaHkpmw7rFb0iSft0xiC-qikcPGLITsW96_I9L_t4n-xQTAC3gsTO1ejKXomOd11SQ3iEVztXa0kE1kTNaXxNYKy7jFfaLINPZJP_er_D4BAf8Gx_tsfgRYxjIMgc0U9LCFIbDj3VOvXUHwyi0keBEcUO2UwKF3t8y5evBjWet-j2ZTa)
9. [mozestudio.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQFK1Q_dqjZTbxn10POUrrMiBDRJ903u8ZhUWtsY09Z7DuvRrgA6wKmfO7PwP5515zIX_cjZwVFer6rJjUkE0hBL6EPu-46-DG0uKNBjXSrqPEH9P8ikb1wnqmvG_iUuZbfIJn3-3GrPtUlGypzPnCUDK7-iDg_laLe10Vo=)
10. [Link](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQG5kjKcsjIUcVomjCoPVTcZA0LQntn3XNwJAOqVupr1FZ7z-1weL9jnDFq_jFXRbTxQhUBbxfruJfJneKCVrCX87viyvkz5TEKjRnHIIKOUzpbGnKnMoULc_6B-Jkk8WlvpnOz0gikerIY54g==)
11. [brianrhea.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGU9FeR-Q4btaX4iwuqPbhcoue6FQvb4cfOfNpx79SYOPE5a9SJjKqTpFAloWgVAWravsmYl6f8LhGI1v1KyZY4CC7L6hP5XnO_srwjKncHtF3Iii4B2BStQ41Ml7gSkm1-qpcKEJWjPYKFGP5ZdaqcGPfVNQ==)
12. [spatialrd.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQFQE4oL9r6Q82S1nOQHlPYsdnuEc6nEyiaon3UPOhW9h82lUZhdw9RyMLmGYX9tsyfHMQYsW82tHU7QsQ2XJrdWds5VWsFv3KLkdgk-yuzeMz2DPU3zk5qSJMa4lQLJP9ynPFBx7vNmCg3c4xnDeOojfroSE_Xba44xVNDsYiGcDREHfYw=)
13. [uxdesign.cc](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHbt0yWQWdg0303G0uMDPxJxFgMZALYSuN1519MNOXrGNC3dmJty2dm_GzlHNLxox52fMcRXNl0KMG4fDq87MILxe3Q4V68qAgvKaF9_KwQeiBA7_22A1kpAe-iDHbv_q937G4LxBSMd9lIBqaDpGQNlvEvlOTp3GyQFeYfz6RyvuBi-ZxTe0gyXzeqXtCl4FP0rXZ8D3_dSP-D6u5vfbJLpR3LqAm7IRLX)
14. [medium.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEOeLFRvuUAuvbpu_KN5b8aHYHn9BNSc-CiiHeEamYABIer7urddBGsfMsXvsxA7G7G86zl3gqyBHktCqgFyrraKhgxEsTWqsKfOJUP6Cy8ZQERXysaDgM1Dq2FRI_4kyRXryQ0wznD8Cy6rbM0CRcdNtsasbNGEtUdjflXYyaHdKADww==)
15. [agilebusiness.org](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQFsnOOkCH13YCkK43l3vXyd3tE1BTYy1q6XeINL-UCt2wUjua7i-Nsx4pLN7JjtLOk3W6VdZAA84rqeEVDAs9C55GJQTSFJhiAxf3EQ5IhNj369Z04ZuPLbEphMBvb54Wze7ElIb0-NmFgoL6Bn-21TXU6jxbx99f5iOkIqA6fasJo10csfdMPczeCgiX0=)
16. [deviniti.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHQuGs-2ltT_goiODGRKIrPo7Hpg_Tg8iMAU0rS913LB02MHs6YSDiHFkst3q1Lb0lrzBvYCw3QbUagyoDClRvjdggLZx1M_nGf3gDMivaeczRZZalHTCDZQ29vcXeHyUkFF6ZUJp5sCk9l-twT0gdAjH336uULCiIchhktRw==)
17. [Link](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHJxFUucsIVhugy_M8vER9r7uTIHqRQnnRXN_idD35YD81e56i7BYmwuXy_1bKdvTnNVwlX3E2WtVZUbC_62UkEDzziuXlkEu-xzeNn-mXUY2Goj7WifeycyBlXIifmhdqrZ3IMWNABTbY-2kSk4W6MuOo2oM6_fDM3pIZdGzI=)
18. [contentdesign.london](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHGIiTlAY6CQ5RJjSeJhZWG4-jsOC_cL7_VFOow1tTYGOkH2dNePhJK6pPsYJg7h3ZVONQ0G28PW-Q7QsLtNYTmG3EP0WMvY3jQLYI29Ls_3nXQCdrwkTYHKcdkmMvXc099u2AK7Oc3WHhDd2tpyEw_fTsvfmHBBD5-4zo3CdnEN3qEnmlIJjh16VNg)
19. [konrad.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGe2uaU1jSUN89uiQBAzqauB5LRyY19DFkDpwMf-6Zcwrewyu-uJRUXLce6jiSYjdXsDruc9gHW6O_sh0AIW8H-uffguxzCDSxqd9FGM_U85xha2ok08fak8f4yLkUiHnJNDw==)
20. [titanapps.io](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHaTH_Lu0MTN6BSocdYLOAZzhVERHoPMeIRRkcsbjksGApjBtBUiKuIpxK4iyi97-eWiSHqQ8M8f_m4uNn-IbnvAVr6ecOgOJhZTUvoqlS-TxLKhY4Al0NVtfAz2A7vG9Q_EnKVWhPv3nZc8x8a-N9QuA==)
21. [atlassian.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEkoVrbii7g27pglSE9-cJv405mFshHWfelC8QxnEyTk2OAuPHw9uEiHLfTQV03wLW-Oi0hh4PDNv6SM6L-AWU5GXhfHBP0zk3XkBk8MYcxtS67p_ZNmmfkU-gyeaIk-WJGpr_GAKRwWuFzy9iv620ZcsqR6xOoIUwoyqBM2IAwUnAPZr_oaacbnaZm8y5_UNO4OcQap1QfvH42cQXQUiE4uONvQXiCnDsvXGzHJ_jvKRReMtRZ)
22. [github.io](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHgNDDrTqFeXJP_MnOQ3_DF2b_4tzywnnxzYKhrAkNqCTJVF-WFUXAp5g1vs3rql1w0wkEHwtoOwLhcVQ-jZx_kirAsRQUNRefSAHs6USzekf1uvPJlNQU4MRIk7n1tE3s2afNxwygNYdXR9oupL-eMCyREg6UU6mYoWsjB-hXndtmUmQctX5lY8Ap72Nd3)
23. [Link](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQERURhI8uOASbtBgn0WYH7V-cq0aBs19-cs3WjCRQrJLa2BXxC1KZXX8DNmXwsSJNFHLVTmkCrIX_kHeFlR4OY-7prSLfvvxB_TAMaTS8-gSagy1uqKe-Kez_xVZW9H00adLhbiwmqnfawY1SjoLl5-qIIn_5x46J6fNGtknsWO-G232Ld06wB8WG2YOBDAqOZX7Aa-_F8=)
24. [medium.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGxBJp_-OphwXdzVXRD1Q5zO3v_RcKLi9sGDDkpcUklWWiGIxm6Rs65w2iOedtZWfuOHsibf1KCiHoxGYJvi0JMkGT8CPc1DwXGCkW3JmWxh_i7KqA4tbiZg_8iWKI7T-grcoH03p7wF-lcEPwp_8srdC2RimZp599YjbTDw3Bi96-0rfmJJFbVsSekDhuEk5c4meHOIEl5lrXEDg==)
25. [withintent.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQF6pMC82sVgEtW9nRL3uxkWZC61tNda1w1ohIDLKouQrD0gPM9UbMjMIyT4lBbrWKNRuYPKZYhbQ-VVAd7kkSPLMSMGw1IoMfjVqw35vOwVPf9OGZZs9-l5k5asBcHMvufZMBkgyNR6c79sfUyPUVb00Ew=)
26. [aakashg.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGwjHewHqRHDmq1GPS2SuEpZcKczZsDUOge5yNOunHAutDBuZwJe2oqGhLYQZHcNSBQEnB6WoZhgfZ3xNQzmGn0VOCLS2xsUviEfG_1jyq2mYRWvEgtDErCOGgW3FRc3_ua6Gn76BMO)
27. [ehandbook.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEBd3b3lrSt_tPm7uvVC1YsZEKNUHjhEd9Pgwr0DaHafZkQa8d7nEJVL8Cz6xrgvbxchqu5K6XbE7OKBrDIVXjjJRWzeRckk2_UjWfJFTHNZe4Qoq1eGL65-lqtv1N-jZlKbY2MsSp_eoqpiOn_SBf9YQWLmT5hJlcQMJhU03qPaFUEQ1IUfwJbKg==)
28. [Link](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGzOPpIJq5KJ4G_eB42s1NL1Cv5FN4N_GTqcvPZfU15SY63MqsQL1m9I_5J171bYA94aUtVcZmfy-N-vxWhIE2QBPNVm_sx1BmIm_Q8JuanBwBYPhxwZqaTlE0kkPnHagUintZ_617JqFU=)
29. [scribd.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQF8VbSHwno9w7IqYE2o8YIVN1Qp8PuMTG4Yo9EOVN6thknDpAY2-Ua9_IcHQibrKGYadFhX7o6YJEWgxVU20zw9tNxyOKqy6nVj7_ig6ypeCo6WgYc2pAEi096kQuq56tPJC1IY3fNO9eTbE_NRU-sJbuqZ3GZ6EDJEwkYd-XaiRlPOlqYsJ4w=)
30. [customlytics.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQFGG4JNXxZPHqv9zxVBeeAjUlBny3_OxUwsybB2fxX6amRs2n3A-iXFlFtg-7yHFnVtOc-PHpkPm_PrS-BYtChTw9lta-AKezucJsBAqUiwDPW48G8rIrU0nyERcl67KtwVewOqjagjAWBrBjSH4ZJLhngrSD2p6s2ycgZczNBqMq63tt3K5vz9mskul8hU4oZ3lYgiLJ_5EQ==)
31. [researchgate.net](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEatyHkN3nITWiT4heKUUonaBVpsmd1-cgDC4-uQRqE3DLdlUfC6CvyXgEI8A-MXmPp01-rhbyzPL_ma_qnegxJflQ9jJ9PfFbllFI-22lUqy4eDvJDOjSXYeOXaE9x-DU6c3y--n9j27MkcBvlh5rujCWeCYMbfl8gS8nnywTATF4iGsvnrhDdIT93i2ZzmQi-WdLp8l6PY-d5FMTZoVxsvlWQZVwg-9igw3bySww5Fc-rMITaWO764M7Bryw=)
32. [easyagile.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQExZ4zglM41ICPtTLC05eKLgWX8R3bKd_r6R5_aGe-zGXD8szl6p2Sxji8ku8eqRkAnbfD9w0T3kwSlTWoauMWsuUSAZDOKg0AkxHIn4WreUmVKkVPRGQm3x5HbcQB4iDR2_zA4Jg==)
33. [avion.io](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQH5qRhgYj_inh9z__JWqY6DpEdC8bwHpk7j87nEeyha99sGsUihW5eTdQZkuJxlE8V1qNG5xJxhox9x5yn5EE7O-un0fCc_rHRJGcMA62EyZCGNOvlqmYfT8-HZBJDU8jVV)
34. [medium.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQE_RYeES7vQ6LKsi8hQBFqPYtHe1zus8r5rBeAA4GYOTx8Ocq4hIDZ0WsCpe4qva1EBu2xbWlTry4t1lMxf3S9CnWONDBjirYpy1AHw-RqAl9c1_vwSMLEE2wkhm_ScEZZ8IFMO4MnGubtZgX3Bd0xU4krDVE-87YKZ7RfnFSou)
35. [mrcet.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHxjy1XPujtAPKQwX8o4Cc2-o01vxTF380SO8XudabVS0v_dpxFxFS9nn3mIVO_yJSCGIzxPLKWw-FqpKPIUowulJQnqZD7fFSDt4lnowRklE92lQ_VjwngI7Keb3nQGjRQpjqZmkDXk5kGLHR2szMSa7Ge5UU9CdzGtWdiegyILCpvwt0_xkF-L85dbwiQ)
36. [spiralscout.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQE-w3FCeg0n4O4iE3MBYOZytHy6MY_W2pSx2fFt8ROEVFYfkwpvWueZIGqJ18fKWOkd7x2Ba7l0tNrv0Lf0g92_Ena2h-xmxS7Fintd7nBnSIVmPhQyO5P0VbKcZ6SiL8Zt6BJQYo6POZ3R_XH2JODkALV1zAZS_nJt6WdTKT_Q0uwEuuZ2AzUiu7jP)
37. [usersnap.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHbK-ve-wos4Sf5KDpi1nRVG2vXXVhJAdM-7Fi85I4VNZYsxwByGW4hOfEbD9lAZh0eohVIAyrS2Xj-pVKQrZUYk1gDDO5WQQR5TNcdiyd92HsLMPKY7LIApQbWinlugPEfdwhvHuf7sLcTAjXrkGTOEN_lup4=)
38. [asana.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGtyLg7yzO8nhHuyLykI_eAwSpV6JLcZRlklTUzbklcC8Am5dTPW7CT97AOnS2UjqbSMCTNIwQ30L4tcUdGGLECUZRQUTz4Sl1cr4nIzXoe6UYhMfr4BnnJ1urXLilP0ytYdw2ccqGz5g==)
39. [medium.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGFpmKhb73M-L0muKH2uY5q3s3VIhktFGbQvSrGBmIPhO8P855QNQwEx-plpE6oPWyrUM0H8_cGs_sub6nUbTLl-8TbDYoZL4YQpzghfKuHwXeZD-wVJIAVVfCh5EjqeoVhIJ0DPgNgDcAwudvFA70V65nijtaZ-RH5UqjBjsZxsvUVkU_c8B3Bh4SHovucwP80OKDyz2H2s77cv7ysig==)
40. [atlassian.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGCqoSx5-NN2nsdeqDHd7IQgJBOwghBdI7Hmt-kcdceIXtzJxMh2Ivx9EykN_zgnMLYdFN6EUhj67EnSLz08Pj1mIu-n_VHFv7B31mkGbwJyjtWQBI-hkgP-LgQjXQtros4nf-WqDzUr-SNg_8e46u7MXqGnYawDHorZnrhgAQGKVajfO191nj2FPmNvWK7-ohw7FfbBeeQoX-7FPal7ugHtSIv-dkqtk2ydFJv3hzm9cjL7_Jqq2mK)
41. [seibert.group](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQG3uM1kRcTsifb7ogMOgtUzrA6aVmCA5Na2VfQwnvkxqLycsCBw2OOjAvaVK_zbDZ8uSihe7iEi9dNQCv8LTh301oQg7GLnUWp7S7owyJG3pFsOf2pePzs1QNxoorDLPlvsSeQdmf85iw3hx-2rahlladSL)
42. [isostech.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGATKEKnz5jkEmyKiGQa6QsemZviEUAVfVZiI9-UxoiHnNDYlQt4ehkTSIOMiRSvzhLBVHhLsLkDMIyVVd46cLsRaJQg-mM4AG8gjO4leOlH5p4hDNnRRrk-ckSgtgfM2hIbfwzxEE-db-2GhNDqSnrH4-ya-PdyOCYHA==)
43. [opinov8.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGrDd-EBhYbrHvFkWA7XrmzQttCowDvosOoXNsLPNps5ruA51OJYzkzgNCbJSxbK9fxC53D_pKzx-rrj2OtfZ4seCquKNm8CkqDVGuBzZcVwCn_MQtqYoa2eXfc3IZNQcrIRIe6qbnY0MJI841x1_3MznzBCsiDWeKRd1Z4At5b)
44. [productleadership.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQED3XQmpcQJD4OjEHQb13uydohhZdqAoAPTZgNC53f2GXL2Hr3PN0IS8wvAklZVkbzpaAPIZC9r4le2KO0-5ce8aLzKYL3ReYkk_kNu1Q_4uutBHp7Q37s9k89dX84hyM5iwnNcQdVJ1FBR6-z1RGko_vz5iwRFb-SoY5VpTe6uIWnknq0=)
45. [karneetk.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGxMx5xYU1hIzPt901KVaJvRQ8sYpIihTm_vJ716bL2GFT7h6KuE5Yvs-DqhD-CamjJi9CgSQTzhKecOcgL6-l9WUGihpYSUIS4fMVviseVpEA2rxr_c_7aglo6MPni)
46. [researchgate.net](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQFsNfo8RFhvdHqTppDFklvNeLPDyUCVChi36Ew1lH3vX1MqixZF4guS3MyDcMRHOzqnttzfWHT2yj6uuYv5oxjztB4K7UOXD5dcasN8hezDtB1qsquPMf-8oSCy_KZZy0heVdxB1KXT171ROUmhDP8EdphFoP2zrYuYgnloKL7XEXH8SFYjUhmHpe41X5gYTeYQxOUFgyvq9aPtyfeHcg2jSXJVJ217OW3NDEPsavjK)
47. [medium.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHn4iJtzDCHZIa9DMZVo_a0rHbPrpQTxnznQgJe5Hv0GzW4AD2LzpO8ijX_IFK9NTKng6HS0Cg2owixB4tij2vsL8lwxovS4dB7pzbueM65p_zHcGTg3WIH7X1tf8XkIwUHjX4von63HnZgXk5xztggukIohmzAfp0=)
48. [ptengine.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQH4nCCIy2tD0FDZ4KRXQVFNrfgKBvOSHaVSSqr6ydvnleHjDNK8OHCQLPY0OvhXTk70APuyUTldl_id53siOCFya6d0q8X2Wuxv8xxMeuk7DdJ1sam-Jolj8q8FUI_5AAsHip_pAOsJgWubpwH5TWPOosorwjw_1U-sicqpP_Bpa6W5WR4vSz4zOjP41PSZ9PmcoSJZ_Rj-bd0kcJ_4kJKi2BFJFpCqa38=)
49. [joninstitute.org](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQF8GitQBkSdNIdqLubK4-2NCSLYXM0ndsG_mqyiNghvqfW6D0x6oQpeVTEzOw71bwugHJlU3ZlKwhByjRcBeYdBTVG5FKnzoQwXkrl1vnjdaGUcWR4VSIYaqYd3FwAVupACvm6yOEkhJYLS3a9qevH6-taxNTww3vCY-MPhTD99g89T5ds=)
50. [savvycomsoftware.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGswF63jWuf8WFM3D4TUDQDLcShG1OYBcoyx1TECYmlqdoCZ4g1Ze7TnLo9U_iwpb7a-kYgKUzPreBfpSWly71eIDe3QrllSxgrFtB_B1oQyseoFTsQfHLqE7xIFotdOB1RSSwZac7pOg==)
51. [medium.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQF7Myza49cMUcTDkwjWwfEOVAaXm7EJfsZyRZr9z6zobs28ZGvDx9P-z5xWeMljG8QWie4FIS644NinzquI14Hxxaw9hNLMBcCpz3hP4zSmF0O_sFzpoBpANdYRCnxrAQ-iVnWusGlWMtPEj7Ta5a9hTVfq_YGcjcflOMHDI1YnKrf_vyuuZwANbHqy9hP-YsdLGQNMNVcMtCJLLah-UEjB5nW4Tvg3WPJf4XFe-BH0jPxclns=)
52. [meegle.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEwnpQVVd8DiQs0zSnChVplQgcS-U7hPJZHCqT_6K5ErbpinS_YR1hIlR_snpp6_nm3CIdxr-16T_lBfL5XYuE2DTQEmLZBJH4-q5XXLOikPqDB_kj9td7vvRZRLRfb4t7DyUCdByfWV6z8f_oa1wS6EqEKQxvRvowLTgdZPHRIKFm0vrj-I73ZhmMkLIggNxM-pZtI2Q==)
53. [nngroup.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQE0t-2O79a5WLdVffITcWBdVD-mpsnvdfnUIZYI9iUeG6sEBXeqonGCH1LZfwhn5ViWTAwVffuY5URuV2rkyJk79k5BXkWEoLf7HnRZuhGd0PQM3vKt72PV6o1wWcZ3GtK37ik5hD8KrUPCo1ikH0QOJlpwIK_J2rbieIhIAw==)
54. [section508.gov](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQFLUgBD-8Q9IvgrUnsuWCriAhE3YZQH2hcL19cGCknyfD_umtXow7pMlV_AaE869diUfHTnrCqKOLdhPrYvvWy0imqODUx8_TMjz8SHzMieKlV-wO1XAr1GAqR92GQKsi_0BeNw4NE=)
55. [arxiv.org](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHgnMS1Tra_ifQoee9RUEp9SQYeDu2X4dtE5I82Xcy8OPmtKfRXnrkvVXDPgIplrctUPLhQ-A-iqZylJny5lDEPyXir1HuOegVyGZ324ReB3gFaHOtqX25dGg==)
56. [w3.org](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGs-r-YpAe0aIrmihtj_XutOj3suVR2cHHBrFvSK_Ksh1oMTQqs6gx1u7FbaHNlaJfaNo8HjJccODlAYKgiR_Rh2cYE2a6q_NSddVzbN-baJdnEIrFwSpu5XZeCytaesqw4MccahprJSVHVmyxE3n5_bbe0)
57. [digitalrhetoriccollaborative.org](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQFY0ifbkdekI8aIry1JuwgHdfEZfvIEFMD2z2L4X7Zq5UvgOtEByyvD2W6Yc1caDWHj21PsUEfJgh_RZI-ZPCYWBY86r-48f0XeqK-mHNX4zKuEK4FLisJsOD3oDlScbV8NMCAAnsn6ZWMwkZh5YOQfWqpR7RtvBv56ZpMG4aMzqKPj20UnzbFvl48ZxO0eSIydk7iiJYSnHgvwaxiyG0fkjo8=)
58. [wcag.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQHP7p3j-K3_q-h2aPNsUpvw8oNgpY9axVHo2opW0bAcy_GyjQjz8xIDz8llDbtAGa6_LXzaH54IctKVWkhrydaN1cAfa-WlK_NSm63ZH2F0Sm-xgce-PK5bLrQfI7I9z3wOyw==)
59. [accessibe.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQF_Rar7HORaCihSVIhgdi1vpZ0k9Bt0Xgte2tzqU3FVKtNJJdnNjT2eJalfIC8fpdSZWi48Sc4-UalVahLEmjfuU2ancLheaIctjNYL3zS4oXRpsa-SrBlygmd1BXUn6Bcm6HQ6NG0xkRii7xjQ-PmnSWLIr3gbGA==)
60. [usablenet.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQGGbomoRfWTF-SJAPBpiGcCrhueSYIQYqkIRm8W_UjLHuHBQQ7Yr2wMpU62gPkEIDiK8rpgKH7on-oZqitSdPRrHIWssVTcvODCAjLo4t5O4Fenr-Oka3ikCn6yV_AdSbAo3DxamqF8kSJEMD4mvOA2DSNAcvgP8OK_nEWFJc2jQROFJVrKRuhy7GkNuwKMiPHUmfzn)
61. [medium.com](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQEkUwcQJbbz-XGGv2pW8TlyTUIIjbRfOqHP4yb5pgKOHLKqcnErzzvWi82lbstLuZOS6tbUxDFvjajScanssbRccKHpKRSll3h5y7PrLkNvmltnM0tWu_t9fyJBlrum7-Y_kyAYirVMVIPy7wQsqijYo9jF_3_QW0j_ZNNfei7kNNZcPbU44t06nvFG__XQZwGmBJg035RO9cIXcGPik7uZM9Mk)
62. [eeoc.gov](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQF-svMPj3LcRmAGeay2wM1e3bBg-2n0ECT8jmyUcJ3Cbe1tY_BVdnJXee2sRg5n7pidSc11t9RxQCcB-Xik9IkjkLm6eD3yZZK3zl_5PB_svR-HiNn-fc82k2ncX2z9igIjwM6lDx7hgPMfXczI6rDc2rF1OGVUdLPuP7oM_1nbTCvkY9yNJw8awgpEA2GqIAs5GoxBWWzOIpiupUurVvTtZByKtgxw-5GO-cOLOBFq5GxYgg==)
63. [nationaldisabilityinstitute.org](https://vertexaisearch.cloud.google.com/grounding-api-redirect/AUZIYQH8WZcmamv-LvoAdUfxwkPmSnJW0ULAUwAd1haDE5zdqW0hJdhWdowy54MW3d3byvBdKepRft0PL6tfdZXq8cVw8eY3Lh5ez1H86eeQ6l0UcEWS2PtDdZhgYc1xzWWnY-05Ak1FzUNWTkdJRRkY5qcAKnSeUsx8Uf1jPfxhs6VnNMckbfanyaVlq8DLR1z3yjdKisAwo-kIRmY3PqqJb4BydqqyBKueiOAiutP-C18XaIu7Q3po5a5fbAQZ8QE=)