--- title: How to Build a Culture of Process Thinking description: Most teams skip process design and go straight to tools. Learn how to build a culture of process thinking and turn mapped workflows into working applications. image: https://blog.kintone.com/hubfs/how%20to%20build%20a%20culture%20of%20process%20thinking%20kintone%20blog.png --- [![Kintone](https://blog.kintone.com/hubfs/KintoneGlobal/svg/logo_kinton_black.svg)](https://www.kintone.com/en-us/) [![Kintone](https://blog.kintone.com/hubfs/KintoneGlobal/svg/logo_kinton_black.svg)](https://www.kintone.com/en-us/) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_search_black.svg) - Product Product![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg)![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - Product ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - [Intro to Kintone](https://www.kintone.com/en-us/intro/) - [Why Kintone](https://www.kintone.com/en-us/why-kintone/) - Features ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - [How Kintone Works](https://www.kintone.com/en-us/how-kintone-works/) - [App Template Library](https://www.kintone.com/en-us/features/app-templates/) - [Extensions](https://www.kintone.com/en-us/features/extensions/) - [Native Kintone Plug-ins](https://www.kintone.com/en-us/features/plugins/) - [Kintone AI](https://www.kintone.com/en-us/features/ai/) - [System Administration](https://www.kintone.com/en-us/features/administration/) - [Security](https://www.kintone.com/en-us/security/) - Solutions Solutions![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg)![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - [Solutions by Department](https://www.kintone.com/en-us/departments/) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - [Operations](https://www.kintone.com/en-us/departments/business-operations/) - [Sales](https://www.kintone.com/en-us/departments/sales/) - [Customer Support](https://www.kintone.com/en-us/departments/customer-support/) - [HR & Admin](https://www.kintone.com/en-us/departments/hr-admin/) - [Marketing](https://www.kintone.com/en-us/departments/marketing/) - [Manufacturing & Retail Management](https://www.kintone.com/en-us/departments/manufacturing-retail-management/) - [IT Support](https://www.kintone.com/en-us/departments/it-support/) - [Solutions by Function](https://www.kintone.com/en-us/functions/) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - [Convert spreadsheets to databases](https://www.kintone.com/en-us/functions/convert-spreadsheets-to-databases/) - [Data Management](https://www.kintone.com/en-us/functions/data-management/) - [CRM & Sales Management](https://www.kintone.com/en-us/functions/crm-sales-management/) - [Project Management](https://www.kintone.com/en-us/functions/project-management/) - [Workflow Management](https://www.kintone.com/en-us/functions/workflow/) - [Remote Work](https://www.kintone.com/en-us/functions/remote-work/) - [Recruitment & Hiring](https://www.kintone.com/en-us/functions/recruitment-hiring/) - [Solutions by Industry](https://www.kintone.com/en-us/industries/) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - [Manufacturing](https://www.kintone.com/en-us/industries/manufacturing/) - [Real Estate](https://www.kintone.com/en-us/industries/real-estate/) - [Retail](https://www.kintone.com/en-us/industries/retail/) - [Education](https://www.kintone.com/en-us/industries/education/) - [Hospitality](https://www.kintone.com/en-us/industries/hospitality/) - [Healthcare](https://www.kintone.com/en-us/industries/healthcare/) - [Nonprofit](https://www.kintone.com/en-us/industries/nonprofit/) - [Solutions by Problem](https://www.kintone.com/en-us/problems/) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - [Streamline Operations and Processes](https://www.kintone.com/en-us/problems/streamline-operations-and-processes/) - [Manage and Organize Business Data](https://www.kintone.com/en-us/problems/manage-and-organize-business-data/) - [Track Project Status and Accountability](https://www.kintone.com/en-us/problems/tracking-project-status-and-accountability/) - [Customer Stories](https://www.kintone.com/en-us/customer-stories/) - [Pricing](https://www.kintone.com/en-us/pricing/) - Resources Resources![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg)![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - [Webinars](https://www.kintone.com/en-us/events/) - [Guidebooks & Videos](https://www.kintone.com/en-us/guidebooks-and-videos/) - [Kintone Support Overview](https://www.kintone.com/en-us/support-overview/) - [Developers](https://kintone.dev/en/) - [Customer Resource](https://www.kintone.com/en-us/for-customers/) - [Blog](https://blog.kintone.com/business-with-heart?__hstc=181257784.34e49544339714832378568b4e02ab6c.1679463564667.1686561291068.1686624267650.55&__hssc=181257784.2.1686624267650&__hsfp=904488742) - Company Company![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg)![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) - - [About Us](https://www.kintone.com/en-us/company/) - [Careers](https://www.kintone.com/en-us/company/careers/) - [Press Center](https://www.kintone.com/en-us/press-center/) - [Contact Us](https://www.kintone.com/en-us/contact/) - ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_search_black.svg)![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_search_red.svg) Search Kintone ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_search_gray.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_login.svg)Log In [Get a Free Trial](https://www.kintone.com/en-us/trial/) [Get a Demo](https://resources.kintone.com/meetings/miri/kintonespecialist?__hstc=181257784.34e49544339714832378568b4e02ab6c.1679463564667.1686561291068.1686624267650.55&__hssc=181257784.2.1686624267650&__hsfp=904488742) - [![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-white.png) ![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-grey.png) ![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-red.png) Business with Heart <3](https://blog.kintone.com/business-with-heart) - [![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-white.png) ![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-grey.png) ![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-red.png) Company + Product](https://blog.kintone.com/company-news) - Business with Heart <3Operations for the Digital First Team - [Company + ProductLatest News from Kintone](https://blog.kintone.com/company-news) - [Business with Heart <3Operations for the Digital First Team](https://blog.kintone.com/business-with-heart) ![](https://blog.kintone.com/hubfs/how%20to%20build%20a%20culture%20of%20process%20thinking%20kintone%20blog.png) [Digital Transformation,](https://blog.kintone.com/business-with-heart/tag/digital-innovation) [Artificial Intelligence,](https://blog.kintone.com/business-with-heart/tag/artificial-intelligence) [Compliance,](https://blog.kintone.com/business-with-heart/tag/compliance) [Workflows,](https://blog.kintone.com/business-with-heart/tag/workflows) # How to Build a Culture of Process Thinking Apr 30, 2026   |   by [Agbaje Feyisayo](https://blog.kintone.com/business-with-heart/author/agbaje-feyisayo) [Tweet](https://twitter.com/share) Most teams do not have a tool problem. They have a process problem. They adopt new platforms, automate tasks, and invest in AI, but the underlying work still runs on tribal knowledge, scattered documents and spreadsheets, and habits that nobody has questioned in years. The tools change. The confusion stays.  A [2025 Lucid survey of 2,200 knowledge workers](https://lucid.co/blog/ai-readiness-survey-2025) found that only 16% of organizations describe their workflows as "extremely well-documented." Nearly half said that undocumented or ad-hoc processes hurt their efficiency on a regular basis. The gap is not in what teams are building with. It is in whether they have defined how their work flows before they start building anything. That gap has a name. It is the absence of process thinking. Process thinking is the practice of seeing work as a series of connected, repeatable steps rather than a collection of one-off tasks. It means asking who is responsible for each step, where information goes next, and what happens when someone is out of the office. It is not a methodology or a framework. It is a mindset that shapes how teams operate, make decisions, and improve over time. This blog breaks down what process thinking looks like in practice and how to start building it into your team's culture. ## **Key Takeaways** - Process thinking is a cultural skill, not a software feature. Tools (even AI) cannot fix what teams have not defined. - Only 16% of organizations say their workflows are well-documented, which means most teams are scaling habits instead of systems. - The biggest barrier to process improvement is not resistance to change. It is the belief that current ways of working are good enough. - Teams that define their processes first get more value from every tool, platform, and automation they adopt afterward. - Building process thinking starts with one workflow, one owner, and one honest conversation about how work gets done. ## **The Cost of Skipping Process Design** When teams skip process design, inefficiency hides in plain sight. It shows up as the same question getting asked every time someone is out of the office. It shows up as three versions of the same tracker living in three different folders, and nobody is sure which one is current. It shows up as new hires taking weeks to become productive because nothing is written down. [McKinsey estimates](https://www.mckinsey.com/capabilities/operations/our-insights) that 20 to 30 percent of operating expenses are lost to process inefficiency. That is not a rounding error. For a mid-sized company with $10 million in annual operating costs, that translates to $2 to $3 million quietly disappearing into rework, miscommunication, and duplicated effort every year. The problem is that inefficiency rarely feels like a crisis. Teams get used to working around broken handoffs, unclear ownership, and undocumented steps. They compensate with extra meetings, follow-up emails, and institutional knowledge that lives in one person's head. The work still gets done, so nobody flags it as a problem. But "getting done" is not the same as "working well." And the cost compounds every time the team grows, a new tool is introduced, or a key person leaves. ## **Why Most Teams Skip Process Thinking** If process thinking is so valuable, why do most teams skip it? There are a few reasons, and none of them involve laziness. The first is speed pressure. When a team is under pressure to deliver, stopping to map out a workflow feels like slowing down. The instinct is to find a tool that solves the immediate pain and figure out the process later. Later rarely comes. The second is the assumption that the tool will impose a process. Many teams believe that adopting a platform will naturally create structure. But a tool without a defined process just digitizes the confusion. The spreadsheet becomes a database. The email chain becomes a notification stream. The underlying disorder stays the same. The third is a structural one. As our COO Yu Tanabe [wrote in a recent LinkedIn article](https://www.linkedin.com/pulse/citizen-developer-never-answer-yu-tanabe-kandc), "This isn't a tooling problem. It's an operating model problem." Tanabe argues that the industry spent years improving tools while ignoring the constraint. Users do not have the time or the mandate to build and maintain systems on top of their actual jobs. The same logic applies to process design. If nobody on the team is responsible for defining how work flows, it will never be defined, regardless of how capable the tools are. ## ****What Process Thinking Looks Like in Practice**** The difference between ad-hoc work and structured work often comes down to language. Teams that think in processes describe their work differently. Instead of "I handle client intake," a process thinker says, "When a new client comes in, here is what happens in order. The sales team logs the deal, the account manager receives a notification, the onboarding checklist gets created, and the client gets their welcome email within 24 hours. If any of those steps stall, the process owner steps in." That level of clarity changes everything. It makes handoffs visible. It makes ownership explicit. It makes onboarding faster because new team members can see how the work flows instead of relying on someone to walk them through it from memory. Process thinking also changes how teams evaluate tools. Instead of asking "what can this platform do?" they ask "does this platform support the way our work actually needs to flow?" That is a fundamentally different question, and it leads to better decisions. ## **How to Start Building Process Thinking Into Your Culture** Building a culture of process thinking does not require a company-wide initiative. It starts small and builds momentum through visible results. ### **Pick one process and make it visible** Choose a workflow that involves multiple people and multiple steps. Use a [process map](https://asq.org/quality-resources/flowchart) to lay out every step, every handoff, and every decision point visually. Map it out in a shared document or on a whiteboard. Write down every step, every handoff, and every decision point. The goal is not perfection. The goal is visibility. Most teams discover at least one step that nobody realized was happening, or one handoff that regularly breaks down. ### **Assign a process owner** Every core workflow needs one person who is responsible for how it runs. That person does not need to do every step. They need to make sure the process is documented, current, and working as intended. Without an owner, processes drift. Steps get added informally. Workarounds become permanent. An owner keeps things honest. ### **Run a quarterly process check** Set aside one meeting per quarter to review your most important workflows. Ask three questions. Is this process still documented accurately? Where did it break down in the last 90 days? What changed in our team or tools that should be reflected in how this works? These meetings are short, but they prevent the slow decay that turns good processes into outdated ones. ### **Build workflows in a structured platform** Once a process is defined, build it in a tool that enforces the steps, permissions, and notifications you have designed. Platforms like Kintone let teams turn a mapped process into a working application with drag-and-drop fields, built-in approval workflows, role-based permissions, and automated notifications. The process comes first. The platform makes it repeatable. ## **Convert Processes into Working Applications** The teams that get the most out of their tools in 2026 will not be the ones with the biggest budgets or the most advanced platforms. They will be the ones that did the unglamorous work of defining how their processes actually run before they started automating anything. Process thinking is the foundation that makes every other investment, whether that is a no-code platform, an AI tool, or a new hire, deliver its full value. Start with one workflow. Make it visible. Give it an owner. And build from there. **Ready to turn your processes into working applications?** [Start a free trial of Kintone](https://kintone.com/en-us/trial/) and see how teams build custom workflow apps without writing code. [![Kintone Free Trial CTA](https://no-cache.hubspot.com/cta/default/1857320/a0c9f62e-cc45-42e5-ade0-913fa2ddcd53.png)](https://cta-redirect.hubspot.com/cta/redirect/1857320/a0c9f62e-cc45-42e5-ade0-913fa2ddcd53) [![](https://blog.kintone.com/hubfs/fe.png)](https://blog.kintone.com/business-with-heart/author/agbaje-feyisayo) About the Author [Agbaje Feyisayo](https://blog.kintone.com/business-with-heart/author/agbaje-feyisayo) Agbaje Feyisayo is a dynamic content marketing expert with over 10 years of experience writing high-converting content across SaaS, technology, AI, and digital transformation. With a strong background in product marketing and storytelling, Agbaje helps top-tier companies turn complex ideas into actionable content that attracts and converts leads. Recommended Posts Up Next [How to Turn Tribal Knowledge Into Team Knowledge](https://blog.kintone.com/business-with-heart/tribal-knowledge-into-team-knowledge) Previous [Vibe No-Coding: Combining The Best of AI and No-Code](https://blog.kintone.com/business-with-heart/vibe-code-and-no-code) [Back to Business with Heart <3 Blog Page](https://blog.kintone.com/business-with-heart) ### Subscribe to Blog #### Recommended Posts [![](https://blog.kintone.com/hubfs/Kintone%20%285%29.png)](https://blog.kintone.com/business-with-heart/how-to-modernize-legacy-processes) Digital Transformation ##### How to Modernize Legacy Processes Without Disrupting Daily Operations Most teams know their legacy processes are holding them back. They are still running intake workflows through spreadsheets, routing approvals through email chains, and manually copying data from one tool to another. These processes are slow, fragile, and hard ... [Read More »](https://blog.kintone.com/business-with-heart/how-to-modernize-legacy-processes) [![](https://blog.kintone.com/hubfs/Kintone%20%281%29-Jun-30-2026-04-48-58-0381-AM.png)](https://blog.kintone.com/business-with-heart/replace-microsoft-project-online-with-no-code-tools) Digital Transformation ##### Replace Microsoft Project Online With No-Code Tools Microsoft Project Online officially retires on September 30, 2026. After more than a decade as a core platform for project scheduling and portfolio management, the service will no longer be available after that date. But for many teams, this retirement is also... [Read More »](https://blog.kintone.com/business-with-heart/replace-microsoft-project-online-with-no-code-tools) [![](https://blog.kintone.com/hubfs/Kintone%20%281%29-4.png)](https://blog.kintone.com/business-with-heart/tribal-knowledge-into-team-knowledge) Digital Transformation ##### How to Turn Tribal Knowledge Into Team Knowledge Every team has someone who just knows how things work. They know which vendor to call when a shipment stalls. They remember the workaround for the billing system glitch that was never fixed. They can close out a monthly report in 20 minutes because they built ... [Read More »](https://blog.kintone.com/business-with-heart/tribal-knowledge-into-team-knowledge) ### Try Kintone For Free! Our clients have built and deployed over 340,000 Kintone applications. Join them by signing up for a free trial–no credit card required–or scheduling a customized product demo. [![Try Kintone for free](https://no-cache.hubspot.com/cta/default/1857320/38781637-01ae-4d81-a227-bf6704b72577.png)](https://cta-redirect.hubspot.com/cta/redirect/1857320/38781637-01ae-4d81-a227-bf6704b72577)[![Schedule a Live Demo](https://no-cache.hubspot.com/cta/default/1857320/97cabdc7-d654-44b7-bf14-68222b115553.png)](https://cta-redirect.hubspot.com/cta/redirect/1857320/97cabdc7-d654-44b7-bf14-68222b115553) [![Kintone](https://blog.kintone.com/hubfs/KintoneGlobal/svg/logo_kinton_black.svg)](https://www.kintone.com/en-us/) U.S. Cambodia China(中文) Hong Kong India Indonesia Korea Laos Malaysia Myanmar Philippines Singapore Taiwan(繁体字) Thailand Viet Nam Japan(日本語) Australia Fiji Kiribati New Zealand Papua New Guinea Samoa Solomon Islands Tonga Tuvalu Vanuatu - [![facebook](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_facebook.svg) ![facebook](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_facebook_color.svg)](https://www.facebook.com/kintoneusa) - [![twitter](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_x.svg) ![twitter](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_x_color.svg)](https://x.com/kintone) - [![LinkedIn](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_linkedin.svg) ![LinkedIn](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_linkedin_color.svg)](https://www.linkedin.com/company/kintoneusa/) - [![Instagram](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_instagram.svg) ![Instagram](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_instagram_color.svg)](https://www.instagram.com/kintoneusa/) - [Terms of Use](https://www.kintone.com/en-us/terms-of-use/) - [Security](https://www.kintone.com/en-us/security/) - [Contact Us](https://www.kintone.com/en-us/contact/) - [Privacy Policy](https://www.kintone.com/en-us/privacy-policy/) - [Partners](https://www.kintone.com/en-us/partners/) Do Not Sell or Share My Personal Information - [Solutions by Department](https://www.kintone.com/en-us/departments/) - [Operations](https://www.kintone.com/en-us/departments/business-operations/) - [Sales](https://www.kintone.com/en-us/departments/sales/) - [Customer Support](https://www.kintone.com/en-us/departments/customer-support/) - [HR & Admin](https://www.kintone.com/en-us/departments/hr-admin/) - [Marketing](https://www.kintone.com/en-us/departments/marketing/) - [Manufacturing & Retail Management](https://www.kintone.com/en-us/departments/manufacturing-retail-management/) - [IT Support](https://www.kintone.com/en-us/departments/it-support/) - [Solutions by Function](https://www.kintone.com/en-us/functions/) - [Convert spreadsheets to databases](https://www.kintone.com/en-us/functions/convert-spreadsheets-to-databases/) - [Data Management](https://www.kintone.com/en-us/functions/data-management/) - [CRM & Sales Management](https://www.kintone.com/en-us/functions/crm-sales-management/) - [Project Management](https://www.kintone.com/en-us/functions/project-management/) - [Workflow Management](https://www.kintone.com/en-us/functions/workflow/) - [Remote Work](https://www.kintone.com/en-us/functions/remote-work/) - [Recruitment & Hiring](https://www.kintone.com/en-us/functions/recruitment-hiring/) - [Solutions by Industry](https://www.kintone.com/en-us/industries/) - [Manufacturing](https://www.kintone.com/en-us/industries/manufacturing/) - [Real Estate](https://www.kintone.com/en-us/industries/real-estate/) - [Retail](https://www.kintone.com/en-us/industries/retail/) - [Education](https://www.kintone.com/en-us/industries/education/) - [Hospitality](https://www.kintone.com/en-us/industries/hospitality/) - [Healthcare](https://www.kintone.com/en-us/industries/healthcare/) - [Nonprofit](https://www.kintone.com/en-us/industries/nonprofit/) - [Solutions by Problem](https://www.kintone.com/en-us/problems/) - [Streamline Operations and Processes](https://www.kintone.com/en-us/problems/streamline-operations-and-processes/) - [Manage and Organize Business Data](https://www.kintone.com/en-us/problems/manage-and-organize-business-data/) - [Track Project Status and Accountability](https://www.kintone.com/en-us/problems/tracking-project-status-and-accountability/) - [Customer Stories](https://www.kintone.com/en-us/customer-stories/) - [Pricing](https://www.kintone.com/en-us/pricing/) - [Native Kintone Plug-ins](https://www.kintone.com/en-us/features/plugins/) - [Intro to Kintone](https://www.kintone.com/en-us/intro/) - [Why Kintone](https://www.kintone.com/en-us/why-kintone/) - [Customer Stories](https://www.kintone.com/en-us/customer-stories/) - [Pricing](https://www.kintone.com/en-us/pricing/) - [How Kintone Works](https://www.kintone.com/en-us/how-kintone-works/) - [App Template Library](https://www.kintone.com/en-us/features/app-templates/) - [Extensions](https://www.kintone.com/en-us/features/extensions/) - [Native Kintone Plug-ins](https://www.kintone.com/en-us/features/plugins/) - [Kintone AI](https://www.kintone.com/en-us/features/ai/) - [System Administration](https://www.kintone.com/en-us/features/administration/) - [Security](https://www.kintone.com/en-us/security/) - [Webinars](https://www.kintone.com/en-us/events/) - [Guidebooks & Videos](https://www.kintone.com/en-us/guidebooks-and-videos/) - [Kintone Support Overview](https://www.kintone.com/en-us/support-overview/) - [Developers](https://kintone.dev/en/) - [Customer Resource](https://www.kintone.com/en-us/for-customers/) - [Blog](https://blog.kintone.com/business-with-heart) - [About Us](https://www.kintone.com/en-us/company/) - [Careers](https://www.kintone.com/en-us/company/careers/) - [Press Center](https://www.kintone.com/en-us/press-center/) - [Terms of Use](https://www.kintone.com/en-us/terms-of-use/) - [Privacy Policy](https://www.kintone.com/en-us/privacy-policy/) - [Partners](https://www.kintone.com/en-us/partners/) - [Contact Us](https://www.kintone.com/en-us/contact/) - Do Not Sell or Share My Personal Information © 2022 Kintone © 2022 Kintone ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Agbaje Feyisayo", "url" : "https://blog.kintone.com/business-with-heart/author/agbaje-feyisayo" }, "dateModified" : "2026-05-22T21:24:01.927Z", "datePublished" : "2026-04-30T16:23:34.000Z", "headline" : "How to Build a Culture of Process Thinking", "image" : [ "https://blog.kintone.com/hubfs/how%20to%20build%20a%20culture%20of%20process%20thinking%20kintone%20blog.png" ], "mainEntityOfPage" : { "@id" : "https://blog.kintone.com/business-with-heart/how-to-build-a-culture-of-process-thinking", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://blog.kintone.com/hubfs/KIN_Logo_H_clr_p_web-4.png" }, "name" : "kintone" } } ```