Edtech
Technical Share - Hackathon Fcamara
Industry
Industry
Edtech
Edtech
Location
Location
Remoto
Remoto
Founded
Founded
2007
2007
Employees
Employees
4000-5000
4000-5000
Challenge
In a large company with multiple projects and team members, it was challenging to assign each professional to a role that aligned with their skill set, as well as to efficiently centralize and distribute knowledge and capabilities across the organization.
Outcomes
The primary objective of this project was to serve as a laboratory for assessing candidate's individual and group competencies. Most squad members received strong evaluations and demonstrated outstanding technical and collaborative skills, resulting in all of them being hired by FCamara. The project that followed then served as the basis for developing an internal tool with a similar purpose.
User Interviews
User Interviews
UI Design
UI Design
Interactive Prototype
Interactive Prototype
Design Critique
Design Critique
User Testing
User Testing
MVP
MVP
Context & Objective
In this hackathon, I was part of a squad made up of three other designers and developers. We had 15 days to deliver a functional MVP. Our challenge was to build a platform capable of centralizing content and fostering connections among team members with varying levels of experience. The objective was to make all materials available in one place, simplify the search for subject-matter experts, accelerate knowledge sharing, and ultimately guide people toward new professional opportunities.
In this hackathon, I was part of a squad made up of three other designers and developers. We had 15 days to deliver a functional MVP. Our challenge was to build a platform capable of centralizing content and fostering connections among team members with varying levels of experience. The objective was to make all materials available in one place, simplify the search for subject-matter experts, accelerate knowledge sharing, and ultimately guide people toward new professional opportunities.
In this hackathon, I was part of a squad made up of three other designers and developers. We had 15 days to deliver a functional MVP. Our challenge was to build a platform capable of centralizing content and fostering connections among team members with varying levels of experience. The objective was to make all materials available in one place, simplify the search for subject-matter experts, accelerate knowledge sharing, and ultimately guide people toward new professional opportunities.
In this hackathon, I was part of a squad made up of three other designers and developers. We had 15 days to deliver a functional MVP. Our challenge was to build a platform capable of centralizing content and fostering connections among team members with varying levels of experience. The objective was to make all materials available in one place, simplify the search for subject-matter experts, accelerate knowledge sharing, and ultimately guide people toward new professional opportunities.
Discover
Initially, we conducted desk research to immerse ourselves in the topic, aiming to understand both the operational context of a technology company and the ecosystem of platforms that provide consultation or issue-resolution capabilities.
CSD
To synthesize the insights gained from the initial research, we developed a matrix of certainties, doubts, and assumptions. This provided an objective overview of the key points to be studied in depth during the next phases of our research.
CSD Matrix
Proto Personas
We created proto-personas based on the initial assumptions that emerged from our desk research and briefing analysis to align our understanding of the target audience at that point. Establishing these proto-personas enabled us to better prioritize the most relevant assumptions during the planning of our research.
We began with two proto-personas: one representing a newly hired employee just starting their career and studies in the field, and another representing a tech lead responsible for assigning team members to projects and addressing their developer's questions.
Proto Personas
Interviews
With some of our assumptions clarified, we developed a semi-structured interview guide to delve deeper into the issues raised and gain a clearer understanding of the user's current journey.
From the interviews, we organized the key findings into an affinity map and identified these emerging patterns:
Existing communication channels were sufficient. Collaboration was already well supported by WhatsApp, Teams, and Discord, so creating a new channel wasn't necessary.
Divergent learning paths. We found differences in how developers and designers learn, which led us to split the proto-persona into two distinct profiles.
Need for anonymity. Some team members sought help outside the company to avoid exposure, prompting us to consider adding anonymity features to the platform.
Gamification to boost engagement. Suggestions arose for gamification elements to engage and reward users and encourage adoption of the tool.
Google Analytics
Discover
Initially, we conducted desk research to immerse ourselves in the topic, aiming to understand both the operational context of a technology company and the ecosystem of platforms that provide consultation or issue-resolution capabilities.
CSD
To synthesize the insights gained from the initial research, we developed a matrix of certainties, doubts, and assumptions. This provided an objective overview of the key points to be studied in depth during the next phases of our research.
CSD Matrix
Proto Personas
We created proto-personas based on the initial assumptions that emerged from our desk research and briefing analysis to align our understanding of the target audience at that point. Establishing these proto-personas enabled us to better prioritize the most relevant assumptions during the planning of our research.
We began with two proto-personas: one representing a newly hired employee just starting their career and studies in the field, and another representing a tech lead responsible for assigning team members to projects and addressing their developer's questions.
Proto Personas
Interviews
With some of our assumptions clarified, we developed a semi-structured interview guide to delve deeper into the issues raised and gain a clearer understanding of the user's current journey.
From the interviews, we organized the key findings into an affinity map and identified these emerging patterns:
Existing communication channels were sufficient. Collaboration was already well supported by WhatsApp, Teams, and Discord, so creating a new channel wasn't necessary.
Divergent learning paths. We found differences in how developers and designers learn, which led us to split the proto-persona into two distinct profiles.
Need for anonymity. Some team members sought help outside the company to avoid exposure, prompting us to consider adding anonymity features to the platform.
Gamification to boost engagement. Suggestions arose for gamification elements to engage and reward users and encourage adoption of the tool.
Google Analytics
Discover
Initially, we conducted desk research to immerse ourselves in the topic, aiming to understand both the operational context of a technology company and the ecosystem of platforms that provide consultation or issue-resolution capabilities.
CSD
To synthesize the insights gained from the initial research, we developed a matrix of certainties, doubts, and assumptions. This provided an objective overview of the key points to be studied in depth during the next phases of our research.
CSD Matrix
Proto Personas
We created proto-personas based on the initial assumptions that emerged from our desk research and briefing analysis to align our understanding of the target audience at that point. Establishing these proto-personas enabled us to better prioritize the most relevant assumptions during the planning of our research.
We began with two proto-personas: one representing a newly hired employee just starting their career and studies in the field, and another representing a tech lead responsible for assigning team members to projects and addressing their developer's questions.
Proto Personas
Interviews
With some of our assumptions clarified, we developed a semi-structured interview guide to delve deeper into the issues raised and gain a clearer understanding of the user's current journey.
From the interviews, we organized the key findings into an affinity map and identified these emerging patterns:
Existing communication channels were sufficient. Collaboration was already well supported by WhatsApp, Teams, and Discord, so creating a new channel wasn't necessary.
Divergent learning paths. We found differences in how developers and designers learn, which led us to split the proto-persona into two distinct profiles.
Need for anonymity. Some team members sought help outside the company to avoid exposure, prompting us to consider adding anonymity features to the platform.
Gamification to boost engagement. Suggestions arose for gamification elements to engage and reward users and encourage adoption of the tool.
Google Analytics
Discover
Initially, we conducted desk research to immerse ourselves in the topic, aiming to understand both the operational context of a technology company and the ecosystem of platforms that provide consultation or issue-resolution capabilities.
CSD
To synthesize the insights gained from the initial research, we developed a matrix of certainties, doubts, and assumptions. This provided an objective overview of the key points to be studied in depth during the next phases of our research.
CSD Matrix
Proto Personas
We created proto-personas based on the initial assumptions that emerged from our desk research and briefing analysis to align our understanding of the target audience at that point. Establishing these proto-personas enabled us to better prioritize the most relevant assumptions during the planning of our research.
We began with two proto-personas: one representing a newly hired employee just starting their career and studies in the field, and another representing a tech lead responsible for assigning team members to projects and addressing their developer's questions.
Proto Personas
Interviews
With some of our assumptions clarified, we developed a semi-structured interview guide to delve deeper into the issues raised and gain a clearer understanding of the user's current journey.
From the interviews, we organized the key findings into an affinity map and identified these emerging patterns:
Existing communication channels were sufficient. Collaboration was already well supported by WhatsApp, Teams, and Discord, so creating a new channel wasn't necessary.
Divergent learning paths. We found differences in how developers and designers learn, which led us to split the proto-persona into two distinct profiles.
Need for anonymity. Some team members sought help outside the company to avoid exposure, prompting us to consider adding anonymity features to the platform.
Gamification to boost engagement. Suggestions arose for gamification elements to engage and reward users and encourage adoption of the tool.
Google Analytics
Define
With the information gathered from the interviews and the validation of several hypotheses, we moved on to defining the solution, beginning with a review of the proto-personas.
Personas
Using the data from our survey and interviews, we validated our user segments by adding a new persona to represent the distinct journeys of developers and UX designers, in addition to the existing tech lead persona.
Reviewed Personas
Prioritization
With the user's pain points defined, we identified opportunities for features that could be implemented in our platform.
Using these solutions and all the research conducted to date, we prioritized these features together with the developers, focusing on those that would deliver the greatest value to the MVP.
Prioritization Mapping
Define
With the information gathered from the interviews and the validation of several hypotheses, we moved on to defining the solution, beginning with a review of the proto-personas.
Personas
Using the data from our survey and interviews, we validated our user segments by adding a new persona to represent the distinct journeys of developers and UX designers, in addition to the existing tech lead persona.
Reviewed Personas
Prioritization
With the user's pain points defined, we identified opportunities for features that could be implemented in our platform.
Using these solutions and all the research conducted to date, we prioritized these features together with the developers, focusing on those that would deliver the greatest value to the MVP.
Prioritization Mapping
Define
With the information gathered from the interviews and the validation of several hypotheses, we moved on to defining the solution, beginning with a review of the proto-personas.
Personas
Using the data from our survey and interviews, we validated our user segments by adding a new persona to represent the distinct journeys of developers and UX designers, in addition to the existing tech lead persona.
Reviewed Personas
Prioritization
With the user's pain points defined, we identified opportunities for features that could be implemented in our platform.
Using these solutions and all the research conducted to date, we prioritized these features together with the developers, focusing on those that would deliver the greatest value to the MVP.
Prioritization Mapping
Define
With the information gathered from the interviews and the validation of several hypotheses, we moved on to defining the solution, beginning with a review of the proto-personas.
Personas
Using the data from our survey and interviews, we validated our user segments by adding a new persona to represent the distinct journeys of developers and UX designers, in addition to the existing tech lead persona.
Reviewed Personas
Prioritization
With the user's pain points defined, we identified opportunities for features that could be implemented in our platform.
Using these solutions and all the research conducted to date, we prioritized these features together with the developers, focusing on those that would deliver the greatest value to the MVP.
Prioritization Mapping
Ideation
After defining the MVP's features and evaluating each for feasibility and product value, we kicked off the ideation phase by researching how these features are implemented in similar-purpose products.
Benchmarking and References
For the prototype ideation phase, we researched similar features in well-known platforms. The main products offering the same or similar functionalities as those identified are Quora, Stack Overflow, LinkedIn, Mentora, Toptal, and Upwork.
Solutions Benchmark
Site Map
Before the wireframing stage, we consolidated our references and created an application map—using a flowchart—to understand how the features would integrate into the system as a whole.
Site-Map
Sketches and Wireframes
After researching references, we each sketched paper wireframes to compare what we considered feasible and then voted on the designs that best aligned with the MVP. This process allowed us to create a low-fidelity prototype, defining the placement of each component and a simple screen-to-screen flow. We adopted a mobile-first strategy, using components that work on both mobile devices and desktops, thereby streamlining development.
Sketches and Wireframes
Prototypes
For the mid-fidelity prototype, we used Material Design components (the design system developed by Google), which sped up the usability-testing process.
At this stage, we focused on establishing the product's navigation, saving time on choosing colors and other aesthetic details.
High Fidelity
Ideation
After defining the MVP's features and evaluating each for feasibility and product value, we kicked off the ideation phase by researching how these features are implemented in similar-purpose products.
Benchmarking and References
For the prototype ideation phase, we researched similar features in well-known platforms. The main products offering the same or similar functionalities as those identified are Quora, Stack Overflow, LinkedIn, Mentora, Toptal, and Upwork.
Solutions Benchmark
Site Map
Before the wireframing stage, we consolidated our references and created an application map—using a flowchart—to understand how the features would integrate into the system as a whole.
Site-Map
Sketches and Wireframes
After researching references, we each sketched paper wireframes to compare what we considered feasible and then voted on the designs that best aligned with the MVP. This process allowed us to create a low-fidelity prototype, defining the placement of each component and a simple screen-to-screen flow. We adopted a mobile-first strategy, using components that work on both mobile devices and desktops, thereby streamlining development.
Sketches and Wireframes
Prototypes
For the mid-fidelity prototype, we used Material Design components (the design system developed by Google), which sped up the usability-testing process.
At this stage, we focused on establishing the product's navigation, saving time on choosing colors and other aesthetic details.
High Fidelity
Ideation
After defining the MVP's features and evaluating each for feasibility and product value, we kicked off the ideation phase by researching how these features are implemented in similar-purpose products.
Benchmarking and References
For the prototype ideation phase, we researched similar features in well-known platforms. The main products offering the same or similar functionalities as those identified are Quora, Stack Overflow, LinkedIn, Mentora, Toptal, and Upwork.
Solutions Benchmark
Site Map
Before the wireframing stage, we consolidated our references and created an application map—using a flowchart—to understand how the features would integrate into the system as a whole.
Site-Map
Sketches and Wireframes
After researching references, we each sketched paper wireframes to compare what we considered feasible and then voted on the designs that best aligned with the MVP. This process allowed us to create a low-fidelity prototype, defining the placement of each component and a simple screen-to-screen flow. We adopted a mobile-first strategy, using components that work on both mobile devices and desktops, thereby streamlining development.
Sketches and Wireframes
Prototypes
For the mid-fidelity prototype, we used Material Design components (the design system developed by Google), which sped up the usability-testing process.
At this stage, we focused on establishing the product's navigation, saving time on choosing colors and other aesthetic details.
High Fidelity
Ideation
After defining the MVP's features and evaluating each for feasibility and product value, we kicked off the ideation phase by researching how these features are implemented in similar-purpose products.
Benchmarking and References
For the prototype ideation phase, we researched similar features in well-known platforms. The main products offering the same or similar functionalities as those identified are Quora, Stack Overflow, LinkedIn, Mentora, Toptal, and Upwork.
Solutions Benchmark
Site Map
Before the wireframing stage, we consolidated our references and created an application map—using a flowchart—to understand how the features would integrate into the system as a whole.
Site-Map
Sketches and Wireframes
After researching references, we each sketched paper wireframes to compare what we considered feasible and then voted on the designs that best aligned with the MVP. This process allowed us to create a low-fidelity prototype, defining the placement of each component and a simple screen-to-screen flow. We adopted a mobile-first strategy, using components that work on both mobile devices and desktops, thereby streamlining development.
Sketches and Wireframes
Prototypes
For the mid-fidelity prototype, we used Material Design components (the design system developed by Google), which sped up the usability-testing process.
At this stage, we focused on establishing the product's navigation, saving time on choosing colors and other aesthetic details.
High Fidelity
Testing and Validation
We conducted the usability test to assess the flow between screens, evaluate tasks, and determine what adjustments were needed for the high-fidelity prototype.
Usability Testing & Critique
Through the Maze platform, we conducted two iterations starting from the initial mid-fidelity prototype, each involving an average of five participants in a moderated testing model. Simultaneously, we held design critique sessions with the hackathon mentors to gather feedback not only from users but also from other perspectives such as UX, QA, and development.
Testing and Validation
We conducted the usability test to assess the flow between screens, evaluate tasks, and determine what adjustments were needed for the high-fidelity prototype.
Usability Testing & Critique
Through the Maze platform, we conducted two iterations starting from the initial mid-fidelity prototype, each involving an average of five participants in a moderated testing model. Simultaneously, we held design critique sessions with the hackathon mentors to gather feedback not only from users but also from other perspectives such as UX, QA, and development.
Testing and Validation
We conducted the usability test to assess the flow between screens, evaluate tasks, and determine what adjustments were needed for the high-fidelity prototype.
Usability Testing & Critique
Through the Maze platform, we conducted two iterations starting from the initial mid-fidelity prototype, each involving an average of five participants in a moderated testing model. Simultaneously, we held design critique sessions with the hackathon mentors to gather feedback not only from users but also from other perspectives such as UX, QA, and development.
Testing and Validation
We conducted the usability test to assess the flow between screens, evaluate tasks, and determine what adjustments were needed for the high-fidelity prototype.
Usability Testing & Critique
Through the Maze platform, we conducted two iterations starting from the initial mid-fidelity prototype, each involving an average of five participants in a moderated testing model. Simultaneously, we held design critique sessions with the hackathon mentors to gather feedback not only from users but also from other perspectives such as UX, QA, and development.
Improvements
After testing, we compiled the user's feedback and observations, then implemented the most significant changes to update the high-fidelity prototype.
Before and After
Initially, the “New Question” button wasn't intuitive for users needing to post a question, so we added a floating action button (FAB) on the main menu.
We revised the menu navigation so the platform's home screen serves more as a central hub for all available features.
We refined the taxonomy, focusing especially on the breadcrumb structure.
We updated the navigation bar to make it clearer to users which section they're in.
Prototype Iterations
Style Guide
Our style guide is based on custom Material Design components.
Style Guide
Accessibility
The chosen theme and colors underwent contrast testing to ensure the application's accessibility.
Accessibility Check
Responsiveness
With all the necessary adjustments for mobile navigation in place, we began developing the prototype by defining breakpoints for desktop and tablet responsiveness—using the same components and scaling them as needed. We also made targeted tweaks like adapting the navigation bar, increasing typography sizes, and converting the FAB into a button for submitting new questions.
Desktop/Tablet Layout
Improvements
After testing, we compiled the user's feedback and observations, then implemented the most significant changes to update the high-fidelity prototype.
Before and After
Initially, the “New Question” button wasn't intuitive for users needing to post a question, so we added a floating action button (FAB) on the main menu.
We revised the menu navigation so the platform's home screen serves more as a central hub for all available features.
We refined the taxonomy, focusing especially on the breadcrumb structure.
We updated the navigation bar to make it clearer to users which section they're in.
Prototype Iterations
Style Guide
Our style guide is based on custom Material Design components.
Style Guide
Accessibility
The chosen theme and colors underwent contrast testing to ensure the application's accessibility.
Accessibility Check
Responsiveness
With all the necessary adjustments for mobile navigation in place, we began developing the prototype by defining breakpoints for desktop and tablet responsiveness—using the same components and scaling them as needed. We also made targeted tweaks like adapting the navigation bar, increasing typography sizes, and converting the FAB into a button for submitting new questions.
Desktop/Tablet Layout
Improvements
After testing, we compiled the user's feedback and observations, then implemented the most significant changes to update the high-fidelity prototype.
Before and After
Initially, the “New Question” button wasn't intuitive for users needing to post a question, so we added a floating action button (FAB) on the main menu.
We revised the menu navigation so the platform's home screen serves more as a central hub for all available features.
We refined the taxonomy, focusing especially on the breadcrumb structure.
We updated the navigation bar to make it clearer to users which section they're in.
Prototype Iterations
Style Guide
Our style guide is based on custom Material Design components.
Style Guide
Accessibility
The chosen theme and colors underwent contrast testing to ensure the application's accessibility.
Accessibility Check
Responsiveness
With all the necessary adjustments for mobile navigation in place, we began developing the prototype by defining breakpoints for desktop and tablet responsiveness—using the same components and scaling them as needed. We also made targeted tweaks like adapting the navigation bar, increasing typography sizes, and converting the FAB into a button for submitting new questions.
Desktop/Tablet Layout
Improvements
After testing, we compiled the user's feedback and observations, then implemented the most significant changes to update the high-fidelity prototype.
Before and After
Initially, the “New Question” button wasn't intuitive for users needing to post a question, so we added a floating action button (FAB) on the main menu.
We revised the menu navigation so the platform's home screen serves more as a central hub for all available features.
We refined the taxonomy, focusing especially on the breadcrumb structure.
We updated the navigation bar to make it clearer to users which section they're in.
Prototype Iterations
Style Guide
Our style guide is based on custom Material Design components.
Style Guide
Accessibility
The chosen theme and colors underwent contrast testing to ensure the application's accessibility.
Accessibility Check
Responsiveness
With all the necessary adjustments for mobile navigation in place, we began developing the prototype by defining breakpoints for desktop and tablet responsiveness—using the same components and scaling them as needed. We also made targeted tweaks like adapting the navigation bar, increasing typography sizes, and converting the FAB into a button for submitting new questions.
Desktop/Tablet Layout
Final Thoughts
After implementing the core features and making the final project adjustments, we moved on to review the remaining secondary requirements identified during prioritization.
Next Steps
As next steps and opportunities, we're exploring integrating Office 365's calendar and Teams calling services to streamline scheduling and communication among collaborators.
Currently, the scoring and ranking system is mocked (non-functional) in the version developed during this hackathon. As a future iteration of the product, the application could be integrated with idea-management platforms like Imagine, developed by FCamara, providing collaborators with a fertile and rewarding environment.
Integration with Other Services
Conclusion
During these 15 days of the hackathon, I had wonderful opportunities to connect with colleagues and mentors who generously shared both technical and soft skills. Applying the knowledge I already had—and everything I learned during the project—was an intense, deeply rewarding endeavor.
Perhaps my greatest challenge was striving for ever more effective communication across different roles. Keeping everyone aligned required dedication beyond prototypes and lines of code, since a lack of connection could have undermined all our efforts. A crucial factor that helped me integrate each phase was a genuine interest in understanding and collaborating with everyone's work, even asynchronously.
More than the technical aspects and deliverables, the real reward of this event was building a project as a team with people of diverse backgrounds and perspectives. I'm not the same person I was 15 days ago.
André Constancio | Alisson Ferreira | Francisco Kleuvys | Leo Rigotto | Mariane Saito
Final Thoughts
After implementing the core features and making the final project adjustments, we moved on to review the remaining secondary requirements identified during prioritization.
Next Steps
As next steps and opportunities, we're exploring integrating Office 365's calendar and Teams calling services to streamline scheduling and communication among collaborators.
Currently, the scoring and ranking system is mocked (non-functional) in the version developed during this hackathon. As a future iteration of the product, the application could be integrated with idea-management platforms like Imagine, developed by FCamara, providing collaborators with a fertile and rewarding environment.
Integration with Other Services
Conclusion
During these 15 days of the hackathon, I had wonderful opportunities to connect with colleagues and mentors who generously shared both technical and soft skills. Applying the knowledge I already had—and everything I learned during the project—was an intense, deeply rewarding endeavor.
Perhaps my greatest challenge was striving for ever more effective communication across different roles. Keeping everyone aligned required dedication beyond prototypes and lines of code, since a lack of connection could have undermined all our efforts. A crucial factor that helped me integrate each phase was a genuine interest in understanding and collaborating with everyone's work, even asynchronously.
More than the technical aspects and deliverables, the real reward of this event was building a project as a team with people of diverse backgrounds and perspectives. I'm not the same person I was 15 days ago.
André Constancio | Alisson Ferreira | Francisco Kleuvys | Leo Rigotto | Mariane Saito
Final Thoughts
After implementing the core features and making the final project adjustments, we moved on to review the remaining secondary requirements identified during prioritization.
Next Steps
As next steps and opportunities, we're exploring integrating Office 365's calendar and Teams calling services to streamline scheduling and communication among collaborators.
Currently, the scoring and ranking system is mocked (non-functional) in the version developed during this hackathon. As a future iteration of the product, the application could be integrated with idea-management platforms like Imagine, developed by FCamara, providing collaborators with a fertile and rewarding environment.
Integration with Other Services
Conclusion
During these 15 days of the hackathon, I had wonderful opportunities to connect with colleagues and mentors who generously shared both technical and soft skills. Applying the knowledge I already had—and everything I learned during the project—was an intense, deeply rewarding endeavor.
Perhaps my greatest challenge was striving for ever more effective communication across different roles. Keeping everyone aligned required dedication beyond prototypes and lines of code, since a lack of connection could have undermined all our efforts. A crucial factor that helped me integrate each phase was a genuine interest in understanding and collaborating with everyone's work, even asynchronously.
More than the technical aspects and deliverables, the real reward of this event was building a project as a team with people of diverse backgrounds and perspectives. I'm not the same person I was 15 days ago.
André Constancio | Alisson Ferreira | Francisco Kleuvys | Leo Rigotto | Mariane Saito
Final Thoughts
After implementing the core features and making the final project adjustments, we moved on to review the remaining secondary requirements identified during prioritization.
Next Steps
As next steps and opportunities, we're exploring integrating Office 365's calendar and Teams calling services to streamline scheduling and communication among collaborators.
Currently, the scoring and ranking system is mocked (non-functional) in the version developed during this hackathon. As a future iteration of the product, the application could be integrated with idea-management platforms like Imagine, developed by FCamara, providing collaborators with a fertile and rewarding environment.
Integration with Other Services
Conclusion
During these 15 days of the hackathon, I had wonderful opportunities to connect with colleagues and mentors who generously shared both technical and soft skills. Applying the knowledge I already had—and everything I learned during the project—was an intense, deeply rewarding endeavor.
Perhaps my greatest challenge was striving for ever more effective communication across different roles. Keeping everyone aligned required dedication beyond prototypes and lines of code, since a lack of connection could have undermined all our efforts. A crucial factor that helped me integrate each phase was a genuine interest in understanding and collaborating with everyone's work, even asynchronously.
More than the technical aspects and deliverables, the real reward of this event was building a project as a team with people of diverse backgrounds and perspectives. I'm not the same person I was 15 days ago.
André Constancio | Alisson Ferreira | Francisco Kleuvys | Leo Rigotto | Mariane Saito
Contact
Interested in my work or have a project in mind? Below, you'll find my contact information and a form where you can describe your idea so we can talk.