TISA (@TISASoftware) profile picture

TISA - Software Engineering Company with operations in United States and Latin America

Houston
Joined November 2010
Photo by TISA (@TISASoftware)Photo by TISA (@TISASoftware)Photo by TISA (@TISASoftware)Photo by TISA (@TISASoftware)Photo by TISA (@TISASoftware)Photo by TISA (@TISASoftware)Photo by TISA (@TISASoftware)Photo by TISA (@TISASoftware)Photo by TISA (@TISASoftware)Photo by TISA (@TISASoftware)
The easy work is already automated. So why does the time still go to emails, scanned documents and exceptions? That's the gap AI process automation is meant to close: rules-based bots handle the predictable steps, AI reads, classifies and recommends, and people approve the decisions that matter. But the research points to process design, not tools. In McKinsey's 2026 State of AI survey, nearly three-quarters of AI high performers report fundamentally redesigning workflows, compared with about one-quarter of other respondents. And Gartner reports fewer than 20% of organizations have mastered measuring their hyperautomation initiatives. Our new article covers: 🔹 Where AI beats rules-based RPA — and where RPA is still the right tool 🔹 How to pick processes actually worth automating 🔹 How to keep humans in the loop without slowing everything down 🔹 The governance and metrics that make automation scale Read the full article: tinyurl.com/23fl7yby #IntelligentAutomation #DigitalTransformation #ITLeadership
1
1
11
Your team adopted AI. They're merging 98% more pull requests. So why hasn't delivery sped up? Faros AI's 2025 analysis of more than 10,000 developers across 1,255 teams found that high-adoption teams completed 21% more tasks and merged 98% more pull requests. Yet review time rose 91%, pull requests grew 154% larger, and lead time didn't improve. Human review had become the bottleneck. Giving everyone a coding assistant and leaving the rest of the process alone doesn't close that gap. AI-first teams start from a harder question: if AI can draft code, tests and documentation in minutes, where should human time actually go? 🔹 What changes in the engineer's job once drafting gets faster? 🔹 How do you keep changes small when AI can generate so much more? 🔹 What should you measure instead of lines of code? The article shows how roles, workflow and review have to be redesigned so more code becomes faster, safer delivery — and the early signs that tell you whether the model is working. Read the full article: tinyurl.com/2daypkly #AIFirst #SoftwareEngineering #ITLeadership
1
1
11
Is your nearshore conversation still about the lowest hourly rate? In Deloitte's Global Outsourcing Survey, cost savings as the main reason for outsourcing fell from 70% in 2020 to 34% in 2024, while access to talent now leads at 42%. Organizations, in Deloitte's words, "are interested in buying capabilities and outcomes, and not hours." In the AI era, that shift changes what IT leaders should evaluate in a nearshore software development partner — and what is easy to miss if the discussion stays on rates. 🔹 Is time-zone overlap treated as a delivery capability, not a perk? 🔹 How does the partner use and govern AI-assisted engineering? 🔹 Does the engagement model match who actually owns the outcome? How a partner answers them usually reveals whether they can share your working hours, review AI-assisted work the same day, and own the outcome you need. The article also covers the delivery, quality and business metrics worth agreeing on before the first sprint. Read the full article: tinyurl.com/26zf3c23 #Nearshoring #SoftwareDevelopment #ITLeadership
1
9
Is your release day still a war room? Most leadership teams know the cycle: a date gets set, the last weeks turn into a scramble, testing gets squeezed, and the launch goes out with known issues and a weekend on standby. Then it repeats. Here's the surprising part: speed and stability aren't a trade-off. More than a decade of DORA research shows that teams that deliver more often also tend to have fewer failed changes and recover faster. Big, infrequent releases feel safer because they seem controlled. In practice, they concentrate risk. And AI raises the stakes. DORA's 2025 research describes AI as an amplifier: it strengthens teams with good delivery practices and exposes the ones without them. Our new article for IT leaders digs into the questions behind fast, stable releases: 🔹 How small should a batch of work really be? (Smaller than most teams think.) 🔹 Why should deploying code and releasing a feature be two separate decisions? 🔹 Which metrics show real progress, and where should you start? When did your last release go out without a weekend on standby? If you can't remember, start here. Read the full article: tinyurl.com/2dyhboxp #SoftwareDelivery #DevOps #ITLeadership
17
Are more AI pilots actually creating more AI value? Most companies no longer need to be convinced that AI matters. Pilots are running in customer service, finance, software engineering and operations, and new requests arrive every week. The harder question is which of them deserve more money. Here's the surprising part: AI ROI rarely comes from running more experiments. Gartner's latest CIO survey found that only 13% of CIOs say their enterprise has realized significant or transformational value from AI so far. In Gartner's words: "Volume is not value." Our new article for IT leaders looks at how to decide which AI pilots to scale, rework or stop: 🔹 What should you define before a pilot starts — and why "explore GenAI in finance" isn't a business case? 🔹 Why do organizations with stop rules outperform, even though most CIOs still don't have them? 🔹 What should you measure instead of total AI spend? Could you name which of your AI pilots are paying off right now? If not, start here. Read the full article: tinyurl.com/2botsmkl #ArtificialIntelligence #AIROI #ITLeadership
1
1
17
What if your metrics look great and your software quality is still invisible? For many organizations, quality only shows up when something breaks: a release slips, a defect reaches customers, or a weekend turns into recovery work. Then leaders ask for answers that should have been visible all along. The warning signs are common. In Harness's State of Software Engineering Excellence 2025, 61% of engineering leaders said code reviews take over a day, and 55% of build pipelines lack proper quality gates. Now add AI coding assistants. DORA's 2025 research describes AI as an amplifier: it strengthens teams with good practices and intensifies the problems of teams without them. Our new article for IT leaders tackles the questions that decide whether quality stays hidden: 🔹 Why do some team models make quality harder to see after go-live? 🔹 Which popular metrics create a false sense of progress? 🔹 What should leaders actually watch, and where should they start? If your board asked how good your software really is, could you show them, or only tell them? Start here. Read the full article: tinyurl.com/2ajqhtj3 #SoftwareEngineering #SoftwareQuality #ITLeadership
1
1
16
What if 10–20% of the budget meant for new products is quietly paying for old shortcuts? That's what CIOs reported in a 2020 McKinsey survey: money earmarked for new products was diverted to resolving tech debt. And it isn't just messy code. A shortcut taken to hit a launch date, an integration built as a quick fix, a framework nobody has upgraded in years. None of it looks urgent on its own. Together, it slows every project that touches it. Here's the twist: the goal isn't zero technical debt. Some debt is a smart business decision. The real danger is the debt nobody decided to take on and nobody is tracking. Our new article for IT leaders takes on the questions most teams avoid: 🔹 Where is your biggest debt really hiding? (Probably not where you think.) 🔹 How do you measure it in business terms, not just engineering metrics? 🔹 Which debt should you pay down, and which is smarter to leave alone? Could you name the systems charging your teams the most "interest" right now? If not, start here. Read the full article: tinyurl.com/29obd2r5 #TechnicalDebt #ITLeadership #SoftwareEngineering
9
Your ERP or CRM needs changes to fit the business. Where those changes live decides how painful the next upgrade will be. "Clean core" is the idea that customizations sit beside the vendor's platform and use its supported APIs and extension points, so upgrades and extensions don't break each other. With vendors shipping updates several times a year, code buried in the core turns every release into a project. Not every change belongs outside, though. Logic that must run in the same transaction can stay in-platform as a supported extension. Portals, mobile apps and AI assistants often fit better side by side, connected through the integration layer. A practical path: 1️⃣ Inventory what you have 2️⃣ Decide: configure, extend or build beside 3️⃣ Make APIs the default contract 4️⃣ Test against every release 5️⃣ Refactor gradually Read the full article: tinyurl.com/2ym4gzo6 #ERP #CRM #CleanCore
1
20
Ask three departments how many active customers you have and you may get three answers. As AI starts working directly from company data, that gap matters more. Master data is the "who" and "what" your business runs on: customers, products, suppliers, locations. Each system keeps its own copy, and over time they drift apart. MDM doesn't have to mean one big central database. Registry, consolidation, coexistence and centralized styles can be combined and evolved domain by domain. Where to start: pick one AI use case and the data domain it depends on, assign owners, and treat data readiness as ongoing work. Read the full article: tinyurl.com/23q8uohf #MasterDataManagement #DataGovernance
6
Your legacy systems still run the business, but every change takes longer, fewer people know the code, and connecting to modern platforms feels like a workaround. Modernizing them doesn't have to mean a multi-year, all-or-nothing rewrite. The strangler fig approach puts a façade in front of the legacy system, builds new services alongside it, and shifts functionality over piece by piece until the old system can be retired, while the business keeps running. Not every app needs the same path, either. Retain and wrap, replatform, refactor incrementally, repurchase, rewrite or retire. Pick by business value, risk and how well the system is understood. Our new guide for IT leaders walks through a five-step roadmap: start with outcomes, find the seams, ship a first slice, plan for data early, and evolve team practices. It also covers where AI-assisted engineering helps and where human review still matters. Read the full article: tinyurl.com/2bhxas27 #LegacyModernization #SoftwareArchitecture
25
The common saying that rules are meant to be broken is especially true of tech endeavors. Nothing restricts creativity more than a set of rules. Here are some rules to be broken. #startupsuccess #digitaltransformation #softwaredevelopment #productdesign tisa-software.com/what-s-up/…
Building a Great UX for Your Mobile App: a Short Guide for Businesses Read the full article: tisa-software.com/what-s-up/… #uidesign #uxdesign #mobileappdesign #DigitalTransformation
2nd day at #CES2020 and much more things to talk about. Autonomous Cars, AR/ VR, and a surprise from Sony linkedin.com/posts/tisa-soft…
@TISASoftware is going to be at #CES2020 in Las Vegas! This city never sleeps, and neither will we this next week during the tech’s biggest show. We will keep you posted with updates from the show, about new trends and technologies that are coming this and the following years
1
Sponsoring #EnterWorks #Engage2019 conference in Denver. Glad to be here next to our Client to discover what's coming next on their platform ecosystem #Enable
1
4
Check out my latest article: How to establish a Company culture with your nearshore Development Team linkedin.com/pulse/how-estab… via @LinkedIn