codechestEduPortal
- The need
- Lessons, assessments and attendance managed across separate tools.
- The product
- A platform bringing lessons, assignments and student management together for teachers and academies.
CodeChest / Global
Different products. Specific jobs to get done.
Explore the workflows behind CodeChest projects: coordinating education, automating a campaign step, matching a delivery route, connecting a local community and collecting event memories via QR code. Use them to discuss the shape of your own product.
Discuss your projectCavabla
- The need
- Sending the same information individually to people commenting on a post.
- The product
- A campaign system that connects post comments to automated private messages.
Tezly
- The need
- Finding a traveller heading in the same direction as a package.
- The product
- A platform connecting senders and travellers by route, with offer and delivery tracking.
Komşuburada
- The need
- Finding nearby updates and local listings in one place.
- The product
- A community platform connecting neighbours through location-based posts and listings.
Balbum
- The need
- Wedding and event photos, videos and guest wishes scattered across different phones.
- The product
- A platform where guests share photos, videos and written or voice wishes in one album via QR code, without signing up.
Look beyond the interface
A useful portfolio review asks who uses the product, what they need to do and how information moves between roles. EduPortal brings education workflows together; it is relevant when a product needs both participant-facing experiences and management tools. Cavabla focuses on a repeated campaign communication step. The implementation questions differ: one concerns shared learning records and roles, while the other concerns a trigger and the action it should produce.
Tezly connects two sides of a workflow, with route matching, offers and delivery status. A similar product needs clear rules for what each participant can see and when the state changes. Komşuburada centres on a neighbourhood community and local content. Its context is different from a single-user utility or an enquiry website. These examples help distinguish a content-led site from a product whose users create and act on information.
Use an example to define your first release
If one project resembles your idea, explain the part that matters to you. It may be the role structure, the matching workflow or the management experience rather than the visible design. Then describe what should be different for your users. Reusing a product pattern does not mean copying its scope: an education business, a marketplace and an internal operations team have different rules and data needs.
The project links open the products’ own websites. Compare the product functions with the work your own users need to complete. For an implementation discussion, bring your intended users, current tools and a sample journey. We can connect that journey to web, mobile or custom software work and identify the smallest release that would be useful in your context.
Next step
Define a useful first release.
Tell us about your users, the problem and the essential journey. Let’s clarify the scope and the next steps.