HOW WE WORK
Intro
Magnetic Ideas is driven by quality. In order to ensure quality in all aspects of our work and in all types of projects, we utilize an agile marketing framework. This framework allows us to prioritize and execute the most vital parts of a project and remain flexible and mindful of the process.
An integral part of this framework are work cycles called sprints. Sprints are 2-4 week cycles where we focus on specific objectives.
Over the years, we’ve learned a lot about how to create marketing solutions and digital assets that achieve business goals as well as delight customers. The sum of these lessons, as well as the ones we learn on a daily basis, has led us to a process that’s anchored in flexibility, collaboration and value.
Jobs we do:
Digital Strategy
Search
Web Development
Social Media
7 Attributes:
- Customer first – We always focus on producing things that are useful and delightful to the customer.
- Learning minded – We are collaborative and curious. Everyone on the team can learn from each other and invest in gaining knowledge from every experience.
- Hybrid Approach – We combine relevant pieces and techniques from existing methods like Scrum, Lean Startup and Design Thinking to deliver tailor-made work.
- Goal Led – Strategies are driven by goals. We prioritize our work based on priorities and factors that are most important to the project stakeholders.
- Solution Driven – We ship marketing and digital product solutions that have real business value to stakeholders.
- Business Aware – We don’t work in a silo and simply check items off a list. Our view is holistic and mindful of the overall business landscape. We work to leverage existing resources and work in parallel to other teams within an organization.
- Future Friendly – We stay in front of the constant changes in technology to produce relevant and timely product.
Roles:
- Stakeholder: The person(s) who is directly impacted by the outcome of the solution.
- Product Owner: This person serves as the “voice of the customer” representing their needs to the team.
- Team Lead: This is the team’s coach. This person is responsible for facilitating communication, optimizing processes and ensuring the team has the resources it needs and is free of obstacles.
- Team Member: These are the people responsible for building the solution. They are involved in every task including architecture, design, copy, analysis, programming and testing.
- Architect: This person’s role is to make decisions and facilitate the overall design and creation of the solution. Many times this is also the team lead.
Process:
Originate + Build + Deploy
Originate: Every project needs a beginning. We sometimes call this phase zero. The main purpose of this phase is to do just enough work to get going in the right direction. Activities we’re likely to perform here are initial requirements modeling, initial architecture modeling, some initial planning, and other organizational activities.
Goals for this phase are:
- form the initial team
- define the project vision
- align with business objectives
- identify risks
- explore the initial scope and release plan
- obtain budget
- identify strategy
- begin creative direction.
Build: The primary purpose of this phase is to create, construct or configure in the case of a consumable solution with sufficient deliverables or to meet the current needs of the project’s stakeholders. We call these build phases sprints.
Goals for this phase are:
- produce potentially consumable solution
- address changing stakeholder needs
- move closer to deployable release
- improve quality
- prove architecture early
Deploy: The purpose of this phase is to successfully release the solution into production (or the marketplace) and measure results. For projects lasting more than one life-cycle, this period serves as a transition activity to begin the next sprint or build phase.
Goals for this phase are:
- ensure solutions are consumable
- release solution
Jobs we do:
Digital Strategy
Search
Web Development
Social Media
7 Attributes:
- Customer first – We always focus on producing things that are useful and delightful to the customer.
- Learning minded – We are collaborative and curious. Everyone on the team can learn from each other and invest in gaining knowledge from every experience.
- Hybrid Approach – We combine relevant pieces and techniques from existing methods like Scrum, Lean Startup and Design Thinking to deliver tailor-made work.
- Goal Led – Strategies are driven by goals. We prioritize our work based on priorities and factors that are most important to the project stakeholders.
- Solution Driven – We ship marketing and digital product solutions that have real business value to stakeholders.
- Business Aware – We don’t work in a silo and simply check items off a list. Our view is holistic and mindful of the overall business landscape. We work to leverage existing resources and work in parallel to other teams within an organization.
- Future Friendly – We stay in front of the constant changes in technology to produce relevant and timely product.
Roles:
- Stakeholder: The person(s) who is directly impacted by the outcome of the solution.
- Product Owner: This person serves as the “voice of the customer” representing their needs to the team.
- Team Lead: This is the team’s coach. This person is responsible for facilitating communication, optimizing processes and ensuring the team has the resources it needs and is free of obstacles.
- Team Member: These are the people responsible for building the solution. They are involved in every task including architecture, design, copy, analysis, programming and testing.
- Architect: This person’s role is to make decisions and facilitate the overall design and creation of the solution. Many times this is also the team lead.
Process:
Originate + Build + Deploy
Originate: Every project needs a beginning. We sometimes call this phase zero. The main purpose of this phase is to do just enough work to get going in the right direction. Activities we’re likely to perform here are initial requirements modeling, initial architecture modeling, some initial planning, and other organizational activities.
Goals for this phase are:
- form the initial team
- define the project vision
- align with business objectives
- identify risks
- explore the initial scope and release plan
- obtain budget
- identify strategy
- begin creative direction.
Build: The primary purpose of this phase is to create, construct or configure in the case of a consumable solution with sufficient deliverables or to meet the current needs of the project’s stakeholders. We call these build phases sprints.
Goals for this phase are:
- produce potentially consumable solution
- address changing stakeholder needs
- move closer to deployable release
- improve quality
- prove architecture early
Deploy: The purpose of this phase is to successfully release the solution into production (or the marketplace) and measure results. For projects lasting more than one life-cycle, this period serves as a transition activity to begin the next sprint or build phase.
Goals for this phase are:
- ensure solutions are consumable
- release solution