This resource is for people:<\/p>\n
It covers:<\/p>\n
Effini<\/a> is a data science organisation that focuses on a people-focused approach to data. Chris is their Head of Engineering and sees projects through from beginning to end. Effini offers solutions that use a wide range of different software.<\/p>\n When you are designing a new impact and evaluation framework, or choosing new systems to work with data. The more complex your data, the more likely you are to need support.<\/p>\n An organisation like Effini can help you work out exactly what you want to measure and share. Then they recommend and configure or build software so that it works well for you.<\/p>\n Chris believes that Effini needs to understand the culture of an organisation to deliver a good data project.<\/strong><\/p>\n He talks about a recent project with the organisation Caring Together as an example.<\/p>\n With strong support from a CEO and a project lead,<\/strong> Effini ran early workshops that explored:<\/p>\n \u201cWe realised that one important metric for the organisation was were they using staff efficiently? Were they making the most of staff time in an area? We were able to show them that this was data that they had. We could combine it with open data sets to help them analyse it”<\/em><\/p>\n Using their processes the teams created KPI’s and prioritised needs<\/strong>. This was successful because of shared understanding.<\/p>\n The solution was a complex Microsoft Azure project to configure, that would then be simple to use. Effini needed to work closely with the digital transformation lead <\/strong>at Caring Together to make it successful.<\/p>\n Katja is a freelance technical lead<\/a>. She works on small and medium scale projects developing apps and websites. She leads small teams and codes in PHP or javascript, but she also works solo. She works flexibility to suit the needs of small charities.<\/p>\n Freelancers who work like Katja often get involved in projects at different scales. They might be:<\/p>\n Katja likes to work on projects that focus on layout, interactions and functionality first.<\/strong> She prefers not to have full visual designs at the beginning of a project.<\/p>\n \u201cIt is about not wanting to waste time\u201d Katja explains. Making changes to a website with fully designed pages can be very time-consuming.<\/p>\n \u201cBut it\u2019s also that it can stop developers thinking properly! We can end up focused on \u2018how do I make it look like this\u2019 when we should be thinking about how it works and what users need.”<\/em><\/p>\n Taking a functionality-first approach takes a brave organisation. Katja has been able to do this recently with The Wildlife Trust’s Nextdoor Nature Hub.<\/p>\n They accepted putting a test website in front of an audience. They understand that genuine alpha and beta testing helps get products right<\/strong>. <\/p>\n Working this way also needs funding that you can use in stages.<\/strong> Once you know that the product is usable and useful, you can add more design elements.<\/p>\n Jonny is the technical lead at William Joseph<\/a>, who designs inclusive products, services and brands. Jonny has a background as a front-end developer, focused on getting the website right on the page. As technical lead, he makes sure all the designers and developers understand the organisation\u2019s needs.<\/p>\n Many charities work with digital agencies of this type to build websites, apps or services. You usually have a technical lead. Depending on your project – the technical lead may have a different speciality.<\/p>\n Some agencies, like William Joseph, have designers that do full brand development work. Other digital agencies may do the design and build of your website but expect you to have brand assets from a graphic designer.<\/p>\n Jonny talks about how projects don\u2019t have to start out well to become great. He describes a project with Parentkind in its early days<\/p>\n \u201cWe were stuck in a loop of getting conflicting feedback on designs from many people. The developers and designers didn\u2019t know what to do. And I\u2019m sure it probably felt to them like we weren’t listening”.<\/em><\/p>\n Both organisations were brave enough to take a step back. They put their focus on setting up the right kind of communication<\/strong>. They created a small core team<\/strong> from both organisations. The group decided to focus on having conversations and building trust<\/strong>. They developed shared tools and worked on a long flow chart of user journeys. Then they explored ways of involving wider stakeholders that were not open forums for criticism.<\/p>\n The project manager from Parentkind and developers from William Joseph spent time co-working<\/strong>. Together they built a collaborative and inclusive decision-making process and a long-term working relationship.<\/p>\n Neontribe<\/a> is an agency that supports tech for good projects. They carry out user research, software development and design. Hannah is a junior developer. She codes in both Python and Javascript depending on the project.<\/p>\n If you work with an agency, you may have junior developers working on your project. They tend to be in their first year or two of coding professionally. They can build things as well as other developers. Often, they have great up-to-date knowledge that can help find solutions to your problems. But they will usually rely on developers in their team with more experience for final decision-making.<\/p>\n Hannah describes feeling trusted<\/strong> as the most crucial thing to making projects work smoothly. Neontribe has been working with NCVO on a wide range of projects since 2017. \u201cWhen we scope a sprint\u201d<\/em> Hannah explains, \u201cThey know that we are telling the truth when we say we can\u2019t fit everything in. They\u2019re used to prioritising\u201d<\/em>. This means that the developers can focus on the actual work – rather than worrying about meeting unrealistic expectations<\/strong>.<\/p>\n Part of building that trust is being able to speak to the right people, often enough.<\/strong> NCVO projects also have regular calls with the key decision-makers.<\/p>\n Hannah recognises that trust must be difficult for charities to feel. This can be particularly true because of the uncertainty that is part of working in an agile way. She wonders \u201cwhat can agencies do, to help charities trust us? How do we let them know that we want to make the best thing we can for them – even when we are saying “no”?\u201d<\/em><\/p>\nWhen do charities work with this kind of developer?<\/strong><\/h3>\n
What\u2019s important to a good project?<\/strong><\/h3>\n
\n
Exploring functionality first – Katja Mordaunt – Freelance<\/strong><\/h2>\n
When do charities work with this kind of developer?<\/strong><\/h3>\n
\n
What\u2019s important to a good project?<\/strong><\/h3>\n
Getting communication right – Jonny Kates – William Joseph<\/strong><\/h2>\n
When do charities work with this kind of developer?<\/strong><\/h3>\n
What\u2019s important to a good project?<\/strong><\/h3>\n
Feeling trusted – Hannah Ouazzane – Neontribe<\/strong><\/h2>\n
When do charities work with this kind of developer?<\/strong><\/h3>\n
What\u2019s important to a good project?<\/strong><\/h3>\n
Resources to help you learn more\/ get started:<\/strong><\/h2>\n
\n
\n