Cto as a service - the top six benefits for your company
Having the right technical leadership can make or break your business, whatever its size. A carefully crafted technology strategy is a must, but not every organisation can afford or even needs a full-time Chief Technology Officer (CTO).
This is where a CTO as a Service comes into play.
But, before we start, what is CTO as a Service?
CTO as a Service or (CTOaaS) employs the services of an experienced technology leader who works with your business on a part-time or project-based basis. They’ll bring the strategic expertise and experience of a full-time CTO without the financial or HR commitments of hiring one permanently. And with the average salary for a full time CTO in the UK in 2024 coming in at just over £100K, it’s a big commitment for any business to make.
So, a more flexible model is particularly attractive to start ups and small to medium-sized businesses (SMEs) that need guidance, but lack the resources or budget for a full-time hire.
And how do you know when it’s the right time to bring one on board?
There are a number of scenarios and signs that indicate your business could benefit from a CTO as a Service arrangement, whether on a project-by-project basis or as a stepping stone to a full time CTO in the future.
So, in this blog post we’ll highlight the top six signs that indicate your organisation would benefit from a using CTO as a Service:
1. Your Business is Growing Rapidly
A nice problem to have, but when your business is growing quickly, your technology needs often struggle to keep up with demand.
You may find you need a swift solution to:
- Build new or optimise existing software platforms
- Integrate new technologies
- Improve scalability and performance
Using CTOaaS can help develop a technology roadmap ensuring your systems can handle growth in a timely manner, preventing costly tech-related miss-haps.
2. You Need A Technology Strategy But Lack The In-House Expertise
Your current leadership team may be brilliant at what they do, but if no one has a technology background, navigating decisions like system architecture, product development or vendor selection can be overwhelming. Plus if it doesn’t sit naturally in anyone’s day-to-day remit, it’s likely to get repeatedly overlooked or not given the attention it requires and deserves.
In this situation, CTO as a Service can act as a bridge, matching business goals to technology solutions to ensure success.
And that’s one example of where a partner like Go Tripod can be invaluable. We’ve been helping SMEs develop and execute their technology roadmaps for more than 15 years over a whole host of industries and our business-minded tech professionals are an amiable crew who can fit into any team to give it the tech boost you need.
3. You’re Preparing for Funding or Investment
If you’re looking to attract investment to fuel your growth, you’ll often find that Investors will scrutinise a company’s technology infrastructure and strategy before making any financial commitment.
Having a seasoned CTO on board as part of your leadership team —even on a part time basis—can:
- Strengthen your investment pitch by showcasing a solid technology vision and well prepared roadmap
- Provide confidence to investors about your technical capabilities and understanding of the impact that a well thought out tech strategy has on your growth strategy as a whole
- Ensure funds are allocated efficiently to the most appropriate technology initiatives
4. Your Product Development is Stalling
If your development team is struggling to meet deadlines, experiencing high teammate turnover or lacking direction, you might need senior technical leadership to help steer them back on the right course and steady the ship.
In this instance CTOaaS can:
- Align development efforts with business goals. Having someone leading the tech team who’s also part of your leadership team will ensure product development supports business goals in terms of budget, launch timing and the features and benefits needed for your minimum viable product (MVP)
- Act as a mentor and guide your development team. Every team needs a great leader however experienced its members are. At Go Tripod, we can provide a part time or temporary CTO with broad leadership experience as well as tech expertise to help you develop your products and successfully get them to market
- Streamline processes to improve productivity. This in turn will improve cost-effectiveness, ultimately boosting your bottom line
5. You’re Facing Security or Compliance Challenges
Whether it’s GDPR compliance, data protection or industry-specific standards, handling technology regulations can be daunting. CTO as a Service brings the expertise to navigate these challenges while implementing best practices to safeguard your systems.
6. You Need to Reduce Costs Without Sacrificing Quality
Hiring a full-time CTO can be expensive, especially if your technology needs don’t require a 40-hour per week commitment. CTOaaS provides the expertise you need on an affordable, flexible basis.
You’re effectively only paying for a CTO for the time and expertise you need, so it’s a lot more cost-effective.
Using a CTO as a Service offering from a seasoned tech company like Go Tripod will have an immediate impact. Our guys can hit the ground running from day one, quickly identifying and addressing technology challenges. The chances are they’ll have worked with companies at a similar growth stage before that will enable them to get on with the job without delay.
And as your business evolves, you can adjust the engagement with your part time CTO accordingly.
The decision to employ a CTO as a Service isn’t about replacing a full-time CTO; it’s about getting the right technical leadership at the right time for the right budget. Whether you’re scaling your business up or tackling complex technical challenges, CTOaaS can provide the guidance you need to drive your business forward—without the long-term financial commitment of a permanent headcount.
If your business finds itself at a crossroads where technology decisions feel too big to handle alone, it may be the perfect time to consider CTO as a Service and the perfect time to talk to us here at Go Tripod.
We’d love to work with you and help you unlock your company’s next phase of growth.
To get in touch today simply email hello@gotripod.com, call us on 0845 475 2487 or complete the form below.
The importance of the project discovery phase in custom software development
Kicking off a custom software development project is an exciting, yet often formidable, prospect. While it presents your business with the opportunity to innovate, introduce workflow efficiencies and improve user and customer experience ratings, it needs to be done utilising proven frameworks and processes in order to maximise its probability of succeeding. However, one crucial early step that often gets overlooked or underestimated is the project discovery phase.
It’s a fundamental phase which lays the groundwork for the project’s overall success, minimising risks and setting the stage for the launch of an impactful, cost-effective digital product.
And, here at Go Tripod, it’s a phase we take extremely seriously, both from a technical perspective and a customer relationship point of view. It’s a mutually beneficial step which sets the scene and enables us to get to know your team as we outline what exactly your software solutions will look like, even before a single piece of code has been written.
So, what is the Discovery Phase?
The discovery phase is the initial step in the software development process, where developers, stakeholders and users collaborate to thoroughly understand the project's objectives, scope, and potential challenges. It involves gathering information, defining requirements and creating a strategic plan that aligns with both business goals, budget and technical constraints.
Why is the Discovery Phase important?
- It clarifies the project vision and objectives
The discovery phase helps everyone involved clearly define the project's purpose and desired outcomes. Through project discovery workshops, interviews and good old-fashioned brainstorming sessions, stakeholders can articulate their expectations and align on a shared vision. This clarity prevents misinterpretations and misaligned objectives that could derail the project at a later stage.
- It identifies key requirements early in the process
Clear, comprehensive gathering of requirements during the discovery phase ensures that the development team understands both the functional and non-functional requirements of the project. This means detailing what the software must do (e.g.process data, integrate with existing systems) and how it must perform (e.g. speed, reliability). Identifying these requirements early on helps in shaping the development roadmap, reducing scope creep and unforeseen feature requests.
- It mitigates risks and challenges
Every project has potential hurdles which will need to be overcome. The discovery phase helps teams pre-emptively identify technical challenges, potential compliance issues and user experience (UX) pitfalls. By acknowledging these challenges early, teams can develop strategies to address them, leading to fewer disruptions during later stages of development.
- It ensures budget and timeline accuracy
One of the most common reasons projects run over budget or beyond their deadlines is a lack of thorough planning. Period.
The discovery phase provides a realistic assessment of time, resources and budget. In understanding the full scope and intricacies of the project upfront, developers can set accurate timelines and budgets that stakeholders can rely on.
- It strengthens stakeholder buy-in and communication
Engaging stakeholders during the discovery phase builds trust and ensures that all voices are heard right from the off. This collaborative approach helps mitigate future conflicts by ensuring that everyone has a comprehensive understanding of the project’s goals and constraints from the beginning. When stakeholders feel involved and informed, they are more likely to stay engaged and supportive throughout the project.
- It creates a blueprint for development
The discovery phase often results in tangible outputs like wireframes, prototypes, user journeys and technical documentation. These elements act as blueprints that guide the development team through the building process, ensuring consistency and adherence to the initial plan.
This is akin to constructing a building with detailed architectural plans versus going in blind; having a map reduces the chances of costly rework and redesign.
Six steps in the Discovery Phase
- Initial consultation and goal setting
The process begins with in-depth discussions between the software development team and stakeholders to understand the business's goals, pain points and expected outcomes.
We love this time at Go Tripod!
It’s a time when we can really get to know your team, seek out what really makes you all tick and what you and your customers really need from the project. And we’re pretty sure, you’ll enjoy this time with us too. We might be software developers, but we’re an amiable bunch with over 15 years’ experience of business processes in all areas, as well as writing code.
- User Research
To design software that meets user needs, it's essential to gather input from the end-users themselves. Again, this is a really insightful and enjoyable part of any project where we conduct interviews, surveys and user testing, which can reveal areas that have an impact on design choices and features.
- Technical Feasibility Analysis
Evaluating the existing technical landscape and determining how the new software will integrate with current systems ensures that there are no surprises once development begins.
Our extensive experience and appetite to continuously learn mean that we’ll be able to utilise the most current and technical platforms and tools.
- Scope Definition
Clearly defining what will be included in the project (and just as importantly, what will not) helps maintain focus and prevent scope creep.
- Prototyping and Wireframing
Visualising the software’s functionality and flow with wireframes and prototypes helps stakeholders and developers align on user experience and overall design before investing significant resources in the full development phase.
- Documentation
The output of the discovery phase is detailed documentation that serves as a roadmap for the entire project. This includes specifications, risk assessments, budget estimates and timelines.
Benefits Post-Discovery Phase
With a thorough discovery phase completed, development teams can enter the design and build stages with confidence. They have a roadmap that guides decision-making, a deep understanding of user expectations and strategies in place to tackle potential challenges. This preparation leads to fewer revisions, a more streamlined development process and ultimately, a beautiful custom-built software product that aligns closely with client needs and performs reliably.
Right back at the beginning of this article we said that the discovery phase of a custom software project is often an area which is overlooked or underestimated.
So, what are the common pitfalls of skipping the discovery phase?
Not something we would ever recommend or do at Go Tripod, but projects that bypass the discovery phase often suffer from:
- Scope Creep: Undefined requirements can lead to constantly changing project goals.
- Budget Overruns: Without an accurate budget from the start, costs can spiral out of control.
- Delayed Timelines: Development teams may encounter unexpected challenges that could have been foreseen with better planning.
- Dissatisfied Stakeholders: A lack of clear communication and engagement early on can lead to disappointment when the final product does not meet expectations.
In conclusion, the discovery phase of a custom software development project is not just a preliminary step— it’s the foundation of a successful project.
Investing time and resources in this phase saves money, reduces risk and creates a strong blueprint that guides the development process. For any business looking to develop custom software, prioritising the discovery phase is a strategic move that pays off in the long run.
By fostering better alignment, informed decision-making and comprehensive planning, the discovery phase ensures that your custom software project delivers the value your business needs, on time and on budget.
We’d love to kick off your next software development project together.
Get in touch today and let’s see how we can build some beautiful software for you that will be impactful and help your business grow…
Simply email hello@gotripod.com, call us on 0845 475 2487 or complete the form below.
What to expect during the custom software development process
Custom software development can feel overwhelming, especially if you're not familiar with the process. However, understanding the steps involved will help you stay in control and ensure you achieve the best outcome for you, your team, your business and your customers!
In this post we’ll walk you through what to expect during each phase of a custom software development project, so you can navigate your journey with confidence.
1. Project Discovery - Initial Consultation and Requirements Gathering
The first step in any custom software development project is understanding exactly what you need. You’ll often hear it referred to as ‘Project Discovery’ and it’s the first vital step in laying the crucial groundwork for a successful project.
It should involve all stakeholders and result in the development of a clear roadmap for the project.
And if this is already sounding a little daunting, fear not!
The selection of an experienced software development team, who understand the demands of today’s multifaceted business processes, will start paying dividends even at this early stage.
They really do play a pivotal role, even at this early stage. It’s so important that they have a clear understanding of your goals and the business problems you’re trying to solve.
But it’s also really important to have a good rapport with your software development team right from the start. You’re going to be working really closely with them throughout the project’s lifespan, so you need to select people you feel you can truly partner with.
At Go Tripod we really pride ourselves in this area. As well as having the development experience and the business acumen to create a tip top software platform for you, we’re a genial down-to-earth bunch who fit into just about any team.
Your chosen development team will kick off by conducting in-depth consultations to gather detailed requirements, which form the foundation for everything that follows.
During this phase, expect the following:
- Stakeholder Interviews: Developers will want to speak to key team members to clarify business needs, pain points, and expectations.
- Business Analysis: Make sure your software development team has someone with clear business experience or a defined project manager to ensure a comprehensive analysis is conducted to understand how the software should align with your business objectives. Put simply you’re looking for a team who can couple market trends with user behaviour and translate that into a successful digital product for your organisation.
- Goal Setting: Clear, measurable goals will be defined, helping guide the development process, assess success and form the basis on on-going monitoring parameters.
2. Planning and Proposal
Once the requirements are understood, the development team will draft a proposal and project plan.
These will typically include:
- Timeline: A rough schedule of development milestones and the overall project timeline.
- Budget: A detailed cost breakdown, including details of any stage payments or milestone triggers.
- Technologies used: Your software development team should provide details of the proposed technologies and platforms that will be used, such as programming languages, frameworks, and hosting solutions.
- Features List/Scope: A comprehensive list of features and functionalities of the software agreed upon during the requirements gathering.
This proposal serves as the go-to document for both you and your development team, ensuring a clear outline of the project’s scope (what’s included and, perhaps more importantly, what’s not!) and expectations moving forward.
3. Design and Prototyping
With a clear plan in place, the design phase can begin.
An experienced software development company will come into its own here.
Expect to see:
- Wireframes: These are basic visual representations of how your software will look, outlining the structure and layout. (Insert GT Example)
- Prototypes: More interactive models that allow you to test and visualize user flows. This stage is essential for user experience (UX) and user interface (UI) design, making sure the software is intuitive and easy to navigate.
You should be looking for a perfect marriage of aesthetics and performance here, to optimise both UX and UI and you should expect to be actively involved in reviewing and providing feedback to ensure the design meets your expectations.
4. Development
This is where the coding begins and the developers really get to work!
The development phase is often broken down into stages:
- Frontend Development: This is the visible part of your application that users interact with (UI/UX).
- Backend Development: This is the "behind-the-scenes" functionality of your software. It includes database interactions, server logic, and any integrations with other systems.
- Agile Methodology: Many developers use an Agile approach, working in short, iterative cycles called “sprints”. But whatever methodology your development team use, you should expect to regularly see progress and have the opportunity to provide feedback.
During this phase, you might not be involved in the technical details, but you should expect regular updates on progress.
5. Testing and Quality Assurance
Before the software is released, it should go through rigorous testing. This ensures that the final product is free from bugs and functions as intended.
Testing includes:
- Unit Testing: This is where individual components or modules of the software are tested for functionality.
- Integration Testing: This testing verifies that different parts of the system work together as intended and, equally, that any integrations with other platforms or systems are seamless.
- User Acceptance Testing (UAT): This is a critical phase, but exciting phase where you and your team get hands-on and test the software in real-world scenarios! Its importance should not be underestimated and you and other key stakeholders will need to be prepared to allocate sufficient time for testing and feedback during UAT.
6. Deployment
Once the software has passed all testing phases, it’s time for deployment. The moment of truth – Go Live - Launch!
The deployment process involves:
- Server Setup: Configuring the environment where the software will ‘live’. This might be a cloud-based system or an on-premises server.
- Data Migration: Moving data from old systems (if applicable) to the new software.
- Launch: Making the software live and accessible to users.
7. Training and Documentation
A key part of a successful software rollout is making sure users are comfortable with the new system. Research shows that the more comfortable users are with software the more successful it will be.
Expect:
- Training Sessions: The extent of the training will depend on the scope and complexity of the system. It may be as simple as a short remotely conducted ‘Teams’ session or it may involve on-site face to face sessions with key stakeholders and their teams facilitating hands-on training to familiarise them with the software’s features, benefits and workflows.
- Documentation: Detailed manuals or guides that explain how to use the software, troubleshoot common issues, and leverage its full potential.
Well-executed training and well written documentation will ensure a smoother transition and higher user adoption rates.
8. Maintenance and Support
Even after the software is live, the development process isn’t completely over. Maintenance and on-going support are critical to address any issues that arise post-launch.
This phase includes:
- Bug Fixes: Addressing any errors or bugs that come to light after the software is in use.
- Updates: Implementing new features or improvements based on user feedback and evolving business needs.
- Technical Support: Ongoing assistance to help with any technical issues or questions your team encounters.
A good development team will offer flexible support plans that suit your needs, from on-call support to regular maintenance updates.
Custom software development is a multi-stage process that requires collaboration, clear communication, and mutual understanding between your business and the team developing the software. By knowing what to expect during each phase — from initial consultation through to deployment and maintenance — you’ll be better equipped to ensure your project’s success.
And by partnering with an experienced development team and staying engaged throughout the process, your business will gain a powerful, tailor-made solution that aligns perfectly with your goals and sets you up for success.
At the top of this post we said we’d walk you through the process of navigating a custom software development project. Well, hopefully, we’ve helped a little in that regard and you have a clearer idea of what to expect.
But it doesn’t stop at a nice blog post for us. Helping our clients navigate bespoke software projects is what we do every day. Our business-minded developers have been doing it for over 15 years and we’d love to help you with your project.
So get in touch today and let’s see how we can build some beautiful software for you that will be impactful and help your business grow…
Simply email hello@gotripod.com, call us on 0845 475 2487 or complete the form below.
10 top tips for choosing the right custom software development agency
There’s no doubt that choosing the right custom software development agency is a big decision and one which can make or break your project.
Whether you're a startup looking to launch your first product, an SME looking to surpass your growth goals or an established enterprise needing to optimise your processes, partnering with the right software agency ensures your vision comes to life efficiently and effectively.
But with so many options available, how do you find the perfect fit for you, your team and your technical needs?
A big question indeed.
And one with potentially far-reaching consequences if you get it wrong.
So, to help ensure you’ve considered all the essentials before making this crucial decision, here are our top tips for choosing the right custom software development agency.
1. Define Your Project Goals and Requirements
Before even starting your search, you’ll need a clear understanding of what you’re trying to achieve.
Ask yourself these key questions:
- What are the specific problems you need to solve with custom software?
- What are the must-have features and functionalities?
- What is your timeline and budget?
By doing this, you'll be able to better communicate your expectations to potential agencies and ensure right from the start that they have the expertise and experience to handle your project.
2. Look for Experience
Experience matters. The right agency should have a strong portfolio and a proven track record. Broad and far-reaching expertise ensures they will be able to understand your unique challenges and anticipate potential roadblocks. It should also ensure they bring best practices to the table that can streamline development and add value to your project.
Things to think about:
- Do they have experience with projects similar to yours?
- Can they showcase successful case studies?
- How familiar are they with the specific technologies your project requires?
3. Check Their Technical Expertise
Technology is constantly evolving, and the agency you choose should be up to date with the latest tools, languages, and frameworks relevant to your project. Their team should have a deep understanding of the technical stack that best suits your needs, whether it's custom web development, mobile apps, cloud services, or enterprise-level software.
Key Considerations:
- What programming languages, frameworks, and platforms do they specialise in?
- Do they offer full-stack development (front-end, back-end, and database)?
- How well do they adapt to emerging technologies (e.g. AI, IoT)?
4. Evaluate Their Communication and Collaboration Approach
A great software development project requires excellent communication and collaboration between your team and the agency. Ensure they have clear communication channels, will provide regular updates, and involve you in key decision-making processes. A collaborative approach leads to better results, faster problem-solving, and fewer misunderstandings.
As we say here at Go Tripod, “Great software starts with great conversations.”
What to look out for…
- How do they handle project management and communication?
- What tools do they use for collaboration (e.g. Slack, Teamwork, Trello)?
- How often will you receive progress updates and reports?
5. Assess Their Development Process and Methodology
The software development lifecycle (SDLC) defines how an agency approaches your project. Agile, Scrum, and DevOps are some of the most popular methodologies that prioritise flexibility and iterative development. Understanding their process helps you gauge whether your prospective software development partner can adapt to changes and meet deadlines without sacrificing quality.
Evaluate the following:
- Do they follow Agile, Scrum, or another iterative methodology?
- How do they manage changes in scope or requirements?
- What is their process for quality assurance and testing?
6. Review Client Testimonials and References
Client reviews, testimonials, and references provide insight into how the agency really works, how reliable they are in practice, and their ability to deliver on promises. Don’t hesitate to ask for references and reach out to past clients for candid feedback about their experience. This will help you spot any red flags and confirm if the agency consistently delivers high-quality work.
Consider the following:
- Can they provide references from previous clients?
- Are there positive reviews on platforms like Clutch or Google?
- How do they handle feedback, setbacks, and challenges?
7. Evaluate Post-Launch Support and Maintenance
Software development doesn't end at launch. You’ll need ongoing support for updates, bug fixes, security patches, and scaling as your business grows. A good custom software development agency should offer post-launch services to ensure the longevity and success of your software.
Consider the following questions:
- What post-launch support and maintenance options do they offer?
- What are their policies for fixing bugs or addressing issues after deployment?
- Do they provide training or documentation for your team?
8. Assess Flexibility and Scalability
Your business and its technology needs will likely evolve over time. Choose a software development company that is flexible and can scale with your project as requirements change or your customer base grows. Whether you're starting with a small MVP (Minimum Viable Product) or need a complex enterprise solution, your chosen software development partner should be able to adapt to your changing needs without compromising quality or timelines.
Assess the following:
- How easily can the agency scale your project as your business grows?
- Are they open to adjusting features or timelines based on new developments?
- Do they offer flexible engagement models (e.g. fixed price, time & materials, retainer)?
9. Understand Their Pricing Structure
Custom software development is an investment, and understanding how an agency structures its pricing is crucial. While it's tempting to go with the lowest quote, remember that quality and expertise come at a cost. Choose an agency that offers transparency in pricing, with no hidden fees or surprises. Ensure their services align with your budget while delivering the quality you need.
Ask yourself these key questions:
- How do they structure their pricing (fixed, hourly, milestone-based)?
- Are there any additional costs for changes in scope or post-launch support?
- What is included in their service agreement or contract?
10. Trust Your Gut
Instinct is key! After evaluating all the technical aspects, it's important to trust your gut feeling too. Building custom software is a collaborative effort, and you'll be working closely with the agency team for an extended period. Choose an agency that not only meets your technical needs but also feels like a good cultural fit for you and your team.
Final Considerations:
- Do you feel comfortable communicating with them?
- Are they genuinely interested in your project's success?
- Do they share your vision and values?
Choosing the right custom software development agency is a critical decision that can significantly impact the success of your project. By defining your needs, evaluating expertise, assessing communication, and reviewing client feedback, you can find an agency that aligns with your goals and delivers exceptional results.
Here at Go Tripod, we’re confident that we tick all those boxes. Our track record is second to none. We're a likeable bunch of highly experienced software developers and commercial brains, with a penchant for creativity and solving business problems with high quality, robust digital solutions for the real world.
Ready to start your custom software journey?
Let’s talk…
- Web App Development
- Mobile App Development
- Custom WordPress Sites
- Digital Transformation
- Legacy Software System Updates
- Paperless Migration
We’d love to help you too!
To learn more about how Go Tripod could help you with your next software development project, simply email hello@gotripod.com, call us on 0845 475 2487 or complete the form below.
Project planning with site maps and user flow diagrams
We're in the early days of planning out a web design-and-build project with a new client. A key part of this process is the creation of a site map.
The Site Map
In its simplest form, a site map is a pictorial representation of the pages required of a website. With smaller websites this list of pages is easy to define and it's not much more of a stretch to group them into a sensible order.
With larger web projects this task can be much more involved and producing a sensible site map relies on a host of other disciplines (like information architecture and user experience design) but the requirements of the job at hand fall mostly into the former camp.
It's worth demonstrating that a sensible site map doesn't merely need to show a breakdown of a website's pages. Instead it should also show how they fit together, where multiple pages might be grouped via dynamic data sources and what kind of elements might be common to every page.
The trick is fitting all of this information into a straight forward infographic that stakeholders can immediately understand (and preferably print).
Enter our case in point (click to expand):
Note that I have used the homepage to define the site-wide header and footer information as well as the main navigation options. It is clear each navigation option represents a top tier page and it is immediately obvious which option includes additional features, pages or sub-sections.
(Strictly speaking the header and footer should be represented on every page, rather than the homepage alone, but to harness the power of an infographic one must expect some inferral ability on the part of our audience.)
The User Flow Diagram
User flow diagrams differ somewhat from site maps in so far as they attempt to demonstrate how a user interacts with a website rather than how the website's contents are hierarchically broken down.
Naturally there is some crossover between these two approaches and again the complexity of a user flow diagram will depend on the complexity of the website (or process) concerned.
One way to think of these things is that whilst both diagrams might utilise boxes and arrows, the user flow diagram is more likely to take the shape of a flow chart.
With our current project, there was a loosely defined need for a restricted client area that would allow logged in users to access (mostly product based) information unavailable to regular visitors.
Whereas our client had been quite clear about what content was required of the front-end, defining this 'restricted area' proved much more elusive. Instead we were given a long list of bullet point thoughts and ideas regarding things they might like.
As it happens, attempting to formalise these loosely defined requirements suits the user flow approach better than the site map approach.
And here is the case in point (click to expand):
Note that this diagram demonstrates how a user might interact with the website and that the flow, in this instance, is shown from left to right.
Starting with the login process, the customer has a number of options; accessing important information available from their dashboard, amending their account details, or drilling down into specific product information.
Again, stakeholders can immediately make sense of what's been proposed. This diagram should, after all, reflect a sensible interpretation of the client's hastily compiled requirement list.
But also, importantly, it serves as an early conceptual blueprint that encourages client feedback. The flow diagram, once finalised, will additionally help formalise the development process.
In conclusion - a collection of carefully thought out infographics can serve as a powerful tool in terms of both defining a new project and improving an existing website or set of software processes.
We work remotely - here's why and here's how
Go Tripod is based at Tremough Innovation Centre in Penryn, Cornwall, but our team members work remotely from locations of their choosing. By giving our staff the freedom to create their own environment, they're able to work smarter and in the way they prefer.
How do we make sure that everyone's on the same page, providing our clients with the best service we can? We've got a suite of tools that help us coordinate and communicate.
It may be seen as old hat but for most companies, including us, email is still a huge part of our operation. It's often the first point of contact for new enquiries, and it's an important mechanism for us to keep in contact with our clients.
Slack
We use Slack as our main means of communicating internally. It's a chat system that allows us to have distinct channels for a variety of different topics and typically we have one for each project. This gives our discussions focus, and allows us to have a history of what's been said (which is searchable for future reference). If we need to bring in a partner, such as a client or a contractor, then we can invite them to a channel as a guest so we can collaborate more easily.
Teamwork
As a project progresses, we track the outstanding items and the evolution of features using a project management tool called Teamwork. Our clients (you could be one too!) get their own login so they can participate in discussions, provide feedback and help us understand any issues. We can also track our time to invoice accurately, and we can see, at-a-glance, the status of any of our current projects.
Appear.in
No matter how fancy our chatroom and project management tools are, sometimes a phone call is the best way of getting a point across. We'll often use appear.in to share a screen between the team to demonstrate a new feature or discuss an implementation, but we'll also use it to let our team catch up. It supports webcams too so we can even look at each other's ugly mugs!
Yodel.io
Since we spend so much time on Slack, we wondered if we could hook phone calls into it. It turns out we can with Yodel.io. When someone calls our office number, if no-one's there to pick up, it'll be routed into Slack where it can be answered in the browser with the press of a button. We can even redirect the call to the correct person's mobile or send it to a customised voice message if we're all unavailable.
By using this set of tools we can work more efficiently and deliver better value to our clients. Working remotely is becoming increasingly popular, and at Go Tripod we've been remote-working advocates since our formation in 2009. In fact, we think that working remotely enables us to provide a better service. Why not try us out?
Managing change requests within the software development process
Software design is a complicated business. To illustrate this point, here is a user flow diagram from a previous project of ours. This level of detail is useful for a number of reasons; it gives the client a real feel for the end product before the need for any coding, it aids in the design process and it helps to formalise pre-development requirements.
Complications can arise when, down the line, it becomes apparent that a functional change is necessary. With all but the most menial of software, this scenario is inevitable.
By practising agile software development we allow for multiple changes during the design and build processes. These changes still need defining, but needn’t derail a project or upset its budget. In the example below what had been specified as an ‘About page’ within the app later became an ‘About section’. (Click the image to enlarge.)
We do our utmost to clearly define our software at the start of a project, but we have a well defined process for managing changes as and when the need arises. This enables us to crack on with development without getting bogged down in specification minutiae.