{"id":5607,"date":"2023-06-20T21:39:43","date_gmt":"2023-06-20T21:39:43","guid":{"rendered":"https:\/\/brainapps.io\/blog\/?p=5607"},"modified":"2026-03-29T04:48:34","modified_gmt":"2026-03-29T04:48:34","slug":"embracing-the-new-normal-navigating","status":"publish","type":"post","link":"https:\/\/brainapps.io\/blog\/2023\/06\/embracing-the-new-normal-navigating\/","title":{"rendered":"The Future of Work: Why Going Back to 2019 Is the Worst Plan &#8211; Practical Models, Mistakes, and 30-90 Day Pilots"},"content":{"rendered":"<h2>Stop trying to &#8220;go back to 2019&#8221;: the biggest planning mistakes about the future of work post\u2011COVID (and why they backfire)<\/h2>\n<p>If your change plan begins with &#8220;let&#8217;s return to how we did things before,&#8221; pause. Trying to rewind to 2019 treats the pandemic as a pause, not a structural shift. That nostalgia is the single biggest planning hazard: it wastes time, drives turnover, and leaves you outmaneuvered by competitors who treat the future of work as a set of trade\u2011offs to manage.<\/p>\n<p>This section cuts to the mistakes managers and HR teams keep repeating, shows the hidden costs, and gives one immediate corrective action you can take today to reduce risk.<\/p>\n<ul>\n<li><strong>Mistake 1 &#8211; Assuming a single &#8220;new normal&#8221;<\/strong>\n<p>Example: a national retailer forces one office schedule across stores and corporate teams-turnover rises where roles could be remote and rent sits unused where it isn&#8217;t needed.<\/p>\n<p>Hidden cost: lost talent, wasted real estate, and brittle operations.<\/p>\n<p>Fix today: map roles by work type (customer\u2011facing, collaborative, heads\u2011down, regulatory) and pilot two to three models per role cluster rather than one blanket policy.<\/p>\n<\/li>\n<li><strong>Mistake 2 &#8211; Treating location as binary<\/strong>\n<p>Example: managers label employees &#8220;onsite&#8221; or &#8220;remote&#8221; and ban flexible hours; caregivers and global hires leave for more adaptable employers.<\/p>\n<p>Hidden cost: lower retention of caregivers, parents, and international talent.<\/p>\n<p>Fix today: adopt a location spectrum-onsite, hybrid\u2011by\u2011role, remote\u2011first, asynchronous-and publish clear exception rules so managers don&#8217;t improvise ad hoc.<\/p>\n<\/li>\n<li><strong>Mistake 3 &#8211; Over\u2011relying on surveillance and proxies for productivity<\/strong>\n<p>Example: keystroke or activity monitoring after a shift to <a href=\"\/course\/remote-work\">Remote work<\/a> causes engagement to plummet and voluntary exits to rise.<\/p>\n<p>Hidden cost: erosion of trust, gaming of metrics, and a decline in creativity.<\/p>\n<p>Fix today: switch to outcome measures (deliverables, cycle time, customer feedback) and run a 30\u2011day pulse survey before buying monitoring tech.<\/p>\n<\/li>\n<li><strong>Mistake 4 &#8211; Outsourcing retraining and ignoring wellbeing<\/strong>\n<p>Example: layoffs followed by a link to generic e\u2011learning-few enroll and even fewer land new roles.<\/p>\n<p>Hidden cost: reputational damage, wasted severance, and a thinner talent pipeline for rehires.<\/p>\n<p>Fix today: fund targeted apprenticeships with wraparound supports (transport stipends, coaching, childcare help) and partner with local providers for placement guarantees.<\/p>\n<\/li>\n<li><strong>Mistake 5 &#8211; One\u2011size\u2011fits\u2011all policies<\/strong>\n<p>Example: a bank applies identical hybrid rules to trading floors and back\u2011office teams, creating safety and operational gaps.<\/p>\n<p>Hidden cost: frustrated managers, service failures, and increased compliance risk.<\/p>\n<p>Fix today: publish policy templates by function and require teams to submit a 60\u2011day operating plan tied to safety and service checklists.<\/p>\n<\/li>\n<li><strong>Mistake 6 &#8211; Underestimating onboarding and belonging costs (remote onboarding included)<\/strong>\n<p>Example: remote hires receive a quick Zoom intro with no buddy program-time\u2011to\u2011productivity doubles and early turnover spikes.<\/p>\n<p>Hidden cost: slow ramp, hidden hiring deficits, and poor retention of early\u2011career staff.<\/p>\n<p>Fix today: formalize remote onboarding with 30\/60\/90 plans, assigned mentors, role\u2011specific learning paths, and local meetups where possible.<\/p>\n<\/li>\n<\/ul>\n<h2>What the &#8220;future of work&#8221; really means post\u2011COVID: drivers, lasting shifts, and signs to watch<\/h2>\n<p>&#8220;Future of work&#8221; describes structural changes in where, how, and why work gets done. The pandemic accelerated shifts that were already underway-similar to how Ford&#8217;s assembly line remapped manufacturing decades earlier. Treat COVID as a catalyst that made new trade\u2011offs visible and executable at scale.<\/p>\n<p>Five enduring shifts to design around:<\/p>\n<ul>\n<li><strong>Location flexibility:<\/strong> remote, hybrid, and asynchronous work patterns are now practical options for many roles.<\/li>\n<li><strong>Occupational mix changes:<\/strong> automation and service\u2011sector shifts are reshaping role demand and increasing the need for workforce reskilling.<\/li>\n<li><strong>Rising value of digital collaboration:<\/strong> tooling, documentation, and asynchronous practices now determine who can work anywhere.<\/li>\n<li><strong>Demand for personalized work experiences:<\/strong> employees expect tailored schedules, benefits, and career paths, not one\u2011size packages.<\/li>\n<li><strong>Geo\u2011mobility and talent redistribution:<\/strong> hiring across regions changes pay bands, candidate pipelines, and workplace design choices.<\/li>\n<\/ul>\n<p>Signals to monitor: remote\u2011job listings, geographic shifts in candidate flow, churn\/Great Resignation indicators, reskilling demand, and time\u2011to\u2011productivity for new hires. Use these signals to prioritize pilots that expose hidden costs early and inform strategic choices.<\/p>  <section class=\"mtry limiter\">\r\n                <div class=\"mtry__title\">\r\n                    Try BrainApps <br> for free                <\/div>\r\n                <div class=\"mtry-btns\">\r\n\r\n                    <a href=\"\/signup?from=blog\" class=\"customBtn customBtn--large customBtn--green customBtn--has-shadow customBtn--upper-case\">\r\n                        Get started                   <\/a>\r\n              <\/a>\r\n                    \r\n                \r\n                <\/div>\r\n            <\/section>   <\/p>\n<h2>Workplace models that actually work &#8211; match strategy to role, not fashion<\/h2>\n<p>Stop copying headlines. Pick a model that fits the work type, customer needs, and culture, then run short, measurable pilots. Below are practical models with who they fit, trade\u2011offs, and quick pilot ideas.<\/p>\n<h3>Model A &#8211; Remote\u2011first (who it fits, pros\/cons, and onboarding tips)<\/h3>\n<p>Fits: distributed knowledge teams (engineering, product, design). Pros: wider talent pool and lower real\u2011estate costs. Cons: requires strong async discipline and larger onboarding investments.<\/p>\n<p>Onboarding and culture tips: structured 30\/60\/90 plans, virtual mentors, clear async documentation standards, quarterly in\u2011person sprints.<\/p>\n<p>Example sectors: open\u2011source software teams, distributed SaaS companies. Pilot idea: move one product team to remote\u2011first for 30-90 days and track bug cycle time, release cadence, and onboarding experience.<\/p>\n<h3>Model B &#8211; Hybrid by role (core teams onsite, others remote)<\/h3>\n<p>Fits: mixed work types (professional services, finance). Pros: balances coordination and flexibility. Cons: can create two classes of employees if unmanaged.<\/p>\n<p>Onboarding and cohesion tips: designate team days, publish role\u2011based hybrid rules, and ensure visibility of career progression for remote staff.<\/p>\n<p>Example sectors: consulting firms, regional banks. Pilot idea: run a 90\u2011day role\u2011by\u2011role hybrid test and measure client satisfaction, staff NPS, and decision speed.<\/p>\n<h3>Model C &#8211; Hub\u2011and\u2011spoke \/ co\u2011working mix<\/h3>\n<p>Fits: distributed employees who need occasional face time (<a href=\"\/course\/sales\">Sales<\/a>, field ops, R&#038;D). Pros: builds local belonging and lowers central office costs. Cons: booking friction and coordination overhead.<\/p>\n<p>Onboarding tips: provide local hubs, coworking subsidies, and quarterly regional meetups to create peer bonds.<\/p>\n<p>Example sectors: biotech R&#038;D networks, regional <a href=\"\/course\/sales\">sales<\/a> organizations. Pilot idea: open one local hub for 60 days and test rituals, booking workflows, and event participation.<\/p>\n<h3>Model D &#8211; Asynchronous\u2011first (document\u2011led, flexible hours)<\/h3>\n<p>Fits: global teams and documentation\u2011heavy workflows. Pros: supports deep work and worldwide hiring. Cons: decisions can slow without clear escalation paths.<\/p>\n<p>Onboarding tips: enforce documentation standards, async rituals (threaded standups), and scheduled office hours for synchronous questions.<\/p>\n<p>Example sectors: distributed open design teams, global support centers. Pilot idea: convert one squad to async\u2011first for a sprint and measure decision latency and developer satisfaction.<\/p>\n<h3>Model E &#8211; In\u2011person\u2011centric with targeted flexibility<\/h3>\n<p>Fits: healthcare, manufacturing, retail-roles that require physical presence. Pros: preserves service quality; Cons: recruiting pressure unless targeted flexibility is offered.<\/p>\n<p>Onboarding tips: cross\u2011train staff, offer compressed schedules, and clarify career ladders tied to shift flexibility.<\/p>\n<p>Example sectors: hospitals, manufacturing plants, frontline retail. Pilot idea: trial a compressed\u2011shift schedule in one unit for 90 days and monitor staffing fill rates and service outcomes.<\/p>\n<h2>Talent, training, and transitions &#8211; what employers and workers must do now<\/h2>\n<p>Passive hiring won&#8217;t solve the labor shift. Reskilling is a change program, not a checkbox. Employers must design targeted retraining aligned to actual open roles, provide portable credentials, and remove barriers to participation. Workers should aim for micro\u2011credentials tied to job descriptions, build a visible portfolio of work, and use network\u2011based outreach to test new paths.<\/p>\n<p>Employer actions: fund apprenticeships with wraparound supports, create portable career maps, redesign roles to include growth opportunities, and offer non\u2011pay retention levers (mentoring, career progression, mental\u2011health support).<\/p>\n<p>Worker actions: pursue short, job\u2011aligned credentials, take on small contract projects to prove skills, and manage transitions with energy\u2011aware steps-start with a 4\u2011week learning sprint before committing to a full career pivot.<\/p>\n<p>Example pilot: a 90\u2011day hospitality\u2011to\u2011healthcare pathway<\/p>\n<ul>\n<li>Skills: basic patient care, documentation, infection control, customer communication.<\/li>\n<li>Partners: community college for accredited modules, local healthcare provider for clinical placement, employer subsidy for training time.<\/li>\n<li>KPIs: 60% placement into entry\u2011level roles within 90 days; time\u2011to\u2011productivity under 120 days; trainee satisfaction > 80%.<\/li>\n<\/ul>\n<h2>Technology, automation, and the human edge &#8211; where to automate and where to invest in people<\/h2>\n<p>Use automation for repetitive, hazardous, or massively scalable tasks. Preserve human roles where judgment, empathy, and complex coordination matter. Pair tools with role\u2011appropriate practices and clear transition support for displaced workers.<\/p>\n<p>Common pitfalls: surveillance tech that erodes trust, tool overload that fragments attention, and biased algorithms that harm vulnerable workers without safeguards.<\/p>\n<p>Recommended tool stacks by model:<\/p>\n<ul>\n<li><strong>Remote\u2011first:<\/strong> async documentation platforms, time\u2011blocking calendars, onboarding and mentorship platforms for remote onboarding.<\/li>\n<li><strong>Hybrid by role:<\/strong> desk booking systems, presence indicators, reliable video, and shared whiteboards.<\/li>\n<li><strong>Hub\u2011and\u2011spoke:<\/strong> coworking reimbursements, local event scheduling, HR scheduling integrations.<\/li>\n<li><strong>Asynchronous\u2011first:<\/strong> threaded messaging, versioned docs, SLA\u2011style response norms.<\/li>\n<li><strong>In\u2011person\u2011centric:<\/strong> shift planning tools, mobile task apps, frontline feedback loops.<\/li>\n<\/ul>\n<p>Privacy and ethics checklist before rolling out monitoring or algorithmic hiring:<\/p>\n<ul>\n<li>Be explicit: define the decision the tool should improve and document why alternatives were rejected.<\/li>\n<li>Assess bias risk and require third\u2011party audits for algorithmic hiring tools.<\/li>\n<li>Set transparent data\u2011retention and access limits and communicate them to staff clearly.<\/li>\n<li>Run a small pilot, measure trust alongside efficiency, and offer opt\u2011outs where feasible.<\/li>\n<\/ul>\n<h2>Roadmap: a staged, low\u2011regret plan for small, mid, and large organizations<\/h2>\n<p>Use five stages: Assess \u2192 Design \u2192 Pilot \u2192 Measure \u2192 Scale. Keep experiments small, time\u2011boxed, and reversible so you learn without creating irreversible costs.<\/p>\n<ol>\n<li><strong>Assess (0-30 days):<\/strong> role mapping, baseline metrics (retention, time\u2011to\u2011productivity). Success = a role catalog and prioritized pilot list.<\/li>\n<li><strong>Design (30-60 days):<\/strong> select models, create onboarding playbooks, define KPIs. Success = playbooks and communications ready for pilots.<\/li>\n<li><strong>Pilot (60-150 days):<\/strong> run 1-3 pilots, collect qualitative and quantitative data. Success = pilot metrics meet thresholds and no critical service regressions.<\/li>\n<li><strong>Measure (150-210 days):<\/strong> evaluate retention, candidate flow by geography, ENPS, and time\u2011to\u2011productivity. Success = validated case studies and clear ROI.<\/li>\n<li><strong>Scale (210+ days):<\/strong> phased rollout with manager training, platform investments, and formal change management. Success = stabilized metrics and improved engagement.<\/li>\n<\/ol>\n<p>Tailored quick roadmaps: small businesses should run lightweight pilots (one hybrid schedule, tightened hiring radius); mid\u2011size firms can test role\u2011by\u2011role hybrids plus training partnerships; enterprises should run geo\u2011strategy experiments with executive sponsors and cross\u2011functional councils.<\/p>\n<p>Sample policy snippets to include in pilots: Day 1 tech setup; Week 1 buddy sessions; Month 1 goals; Month 3 review. Meeting rules: agendas required, 25-50 minute defaults, optional meeting\u2011free blocks. Documentation standards: decision logs, meeting notes, tagged owners and next steps.<\/p>\n<p>Common metrics to track: retention, time\u2011to\u2011productivity for new hires, candidate flow by geography, ENPS, and a blended productivity + wellbeing indicator (deliverables paired with <a href=\"\/course\/burnout\">Burnout<\/a>\u2011risk surveys). These metrics tell you whether to scale, pivot, or stop a pilot.<\/p>\n<p><strong>Conclusion:<\/strong> the future of work isn&#8217;t a single destination or a slogan. It&#8217;s a set of trade\u2011offs that leaders must manage deliberately. Avoid nostalgic fixes and one\u2011size policies. Match models to roles, invest in onboarding and reskilling, use technology with a human\u2011first ethic, and run short experiments with clear metrics.<\/p>\n<blockquote>\n<p><strong>Is <a href=\"\/course\/remote-work\">remote work<\/a> the same as the future of work?<\/strong><\/p>\n<p>No. Remote work is one element of a broader set of changes-hybrid patterns, reskilling, occupational shifts, and workplace design. Treat remote work as the right strategy for some roles, not a universal solution.<\/p>\n<p><strong>How should I choose between remote\u2011first and hybrid for my team?<\/strong><\/p>\n<p>Map roles by work type (customer\u2011facing, collaborative, heads\u2011down, regulatory), evaluate customer and operational needs, and pilot the model that fits each role cluster. Measure service outcomes and time\u2011to\u2011productivity before scaling.<\/p>\n<p><strong>What jobs are most at risk of automation after COVID?<\/strong><\/p>\n<p>Roles with repetitive, rule\u2011based tasks are most exposed. Focus on reskilling pathways and targeted apprenticeships rather than assuming layoffs or offshoring are the only options.<\/p>\n<p><strong>How do you onboard and build belonging remotely?<\/strong><\/p>\n<p>Use structured 30\/60\/90 plans, virtual mentors, documented rituals, and occasional in\u2011person sprints or local meetups to accelerate belonging and time\u2011to\u2011productivity.<\/p>\n<p><strong>Can small businesses compete for talent against remote\u2011first giants?<\/strong><\/p>\n<p>Yes-by offering differentiated value (local community, faster career progression, targeted flexibility) and running quick pilots that show a strong candidate experience.<\/p>\n<p><strong>How do we measure productivity without harming morale?<\/strong><\/p>\n<p>Favor outcome\u2011based metrics (deliverables, cycle time, customer satisfaction) over surveillance proxies. Publish measurement rules, conduct pulse surveys, and allow opt\u2011outs or appeals for monitoring tools.<\/p>\n<p><strong>What short\u2011term pilots actually show meaningful results?<\/strong><\/p>\n<p>Run a 30-90 day pilot on one team with clear KPIs (time\u2011to\u2011productivity, ENPS, customer metrics), include a baseline or control, document onboarding steps, and define success thresholds up front.<\/p>\n<\/blockquote>\n  <section class=\"landfirst landfirst--yellow\">\r\n<div class=\"landfirst-wrapper limiter\">\r\n<img decoding=\"async\" src=\"https:\/\/brainapps.io\/blog\/wp-content\/themes\/reboot_child\/bu2.svg\" alt=\"Business\" class=\"landfirst__illstr\">\r\n<div class=\"landfirst__title\">Try BrainApps <br> for free<\/div>\r\n<div class=\"landfirst__subtitle\">\r\n\r\n\r\n<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"24\" viewBox=\"0 0 24 24\"><path d=\"M20.285 2l-11.285 11.567-5.286-5.011-3.714 3.716 9 8.728 15-15.285z\"\/><\/svg> 59 courses\r\n<br>\r\n<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"24\" viewBox=\"0 0 24 24\"><path d=\"M20.285 2l-11.285 11.567-5.286-5.011-3.714 3.716 9 8.728 15-15.285z\"\/><\/svg> 100+ brain training games\r\n <br>\r\n<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"24\" height=\"24\" viewBox=\"0 0 24 24\"><path d=\"M20.285 2l-11.285 11.567-5.286-5.011-3.714 3.716 9 8.728 15-15.285z\"\/><\/svg> No ads\r\n\r\n <\/div>\r\n<a href=\"\/signup?from=blog\" class=\"customBtn customBtn--large customBtn--green customBtn--drop-shadow landfirst__btn\">Get started<\/a>\r\n<\/div>\r\n<\/section>  ","protected":false},"excerpt":{"rendered":"<p>Stop trying to &#8220;go back to 2019&#8221;: the biggest planning mistakes about the future of work post\u2011COVID (and why they backfire) If your change plan begins with &#8220;let&#8217;s return to how we did things before,&#8221; pause. Trying to rewind to 2019 treats the pandemic as a pause, not a structural shift. That nostalgia is the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1643],"tags":[],"yst_prominent_words":[],"class_list":["post-5607","post","type-post","status-publish","format-standard","","category-leadership-and-management"],"acf":[],"_links":{"self":[{"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/posts\/5607","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/comments?post=5607"}],"version-history":[{"count":0,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/posts\/5607\/revisions"}],"wp:attachment":[{"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/media?parent=5607"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/categories?post=5607"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/tags?post=5607"},{"taxonomy":"yst_prominent_words","embeddable":true,"href":"https:\/\/brainapps.io\/blog\/wp-json\/wp\/v2\/yst_prominent_words?post=5607"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}