(1) People (2) Process…then (3) Technology
Before you even think about tools to help improve your business, first determine whether the operational bottleneck is people, process, or technology. Often, businesses use technology to mask an issue with people or process.
The key to the successful implementation of any new tool in business is understanding your operations, processes and procedures. Failure to do so will result in a tool being layered on top of a poorly understood, implemented or followed process – this leads to frustration and increased inefficiencies.
Map out your processes and start asking “why” at each step. Once this is done, you will be able to more easily determine whether a new tool will add value or simply add complexity and cost.
Remember: just because it’s the most talked about ‘thing’ today doesn’t mean that it’s a fit for your organization!
Below are some questions to ask when evaluating new technology tools for you business.
- Define Your Business Needs
- What problem are we solving?
☐ Improve productivity (e.g., faster task completion)
☐ Enhance collaboration (e.g., team sharing or communication)
☐ Streamline workflows (e.g., note-taking, project tracking)
☐ Improve security and compliance - What tasks will the tool support?
☐ Daily operations (e.g., email, scheduling)
☐ Specialized work (e.g., design, writing, data entry)
☐ Mobility (e.g., on-the-go use vs. desk-based) - Example: Will iPads support mobile client meetings, or do laptops better handle heavy software?
- Assess Staff Technology Skills
- What is the current skill level of my team?
☐ Beginner (basic navigation, minimal tech use)
☐ Intermediate (comfortable with common tools like email, spreadsheets)
☐ Advanced (can adapt to new systems quickly) - Will training be required?
☐ Yes—Estimate time/cost: __________
☐ No—Staff can adopt with minimal guidance - Example: Can staff easily switch to reMarkable notepads for note-taking, or do they need laptop familiarity?
- Match Tools to Wants and Goals
- What do we want from this tool?
☐ Portability (e.g., iPads/reMarkable for mobility)
☐ Power (e.g., laptops for multitasking)
☐ Simplicity (e.g., reMarkable for focused note-taking)
☐ Other: ___________________________ - Does it align with long-term goals?
☐ Supports growth (e.g., scalable software)
☐ Future-proofs tech (e.g., upgradable devices) - Example: Do reMarkable notepads meet a goal of reducing paper use?
- Evaluate Costs vs. Value
- What’s the total cost?
☐ Upfront purchase: $__________
☐ Ongoing (subscriptions, maintenance): $__________
☐ Training/support: $__________ - What’s the expected return?
☐ Time saved: _____ hours/week
☐ Revenue boost: $__________
☐ Efficiency gains: ___________________ - Example: Are iPads’ portability worth the cost vs. laptops’ versatility vs. reMarkable’s focus/simplicity?
- Check Compatibility and Integration
- Does it work with existing systems?
☐ Yes—Seamless with current software/hardware/workflow
☐ No—Requires workarounds or new investments - Can it connect across the team?
☐ Supports file sharing, cloud access, etc.
☐ Limited to standalone use - Example: Will reMarkable sync with our cloud storage, or do laptops integrate better?
- Test Usability and Flexibility
- Is it easy to use?
☐ Intuitive for staff with current skills
☐ Complex—may frustrate users - Can it adapt as needs change?
☐ Flexible (e.g., laptops for multiple roles)
☐ Niche (e.g., reMarkable for specific tasks) - Example: Are iPads too limited compared to laptops for future tasks?
- Consider Risks and Support
- What are the risks?
☐ Downtime if it fails
☐ Security vulnerabilities
☐ Learning curve delays - Is support available?
☐ Vendor support (phone, email, etc.)
☐ Internal or outsourced IT can handle issues - Example: Can we troubleshoot reMarkable issues in-house?
- Gather Team Input
- Have I asked my staff?
☐ Surveyed preferences (e.g., iPads vs. laptops)
☐ Tested with a small group - Will they adopt it?
☐ Enthusiastic about the tool
☐ Resistant—may need convincing - Example: Does the team prefer reMarkable’s simplicity or laptops’ familiarity?
- Decision & Gut check
- Based on this checklist, should we adopt this tool?
☐ Yes—It meets needs, fits skills, and adds value
☐ No—Costs outweigh benefits or it’s a mismatch - Next steps:
☐ Pilot test with a few users
☐ Research alternatives
☐ Implement and train
